fiji CLI

The release tarball ships a bin/fiji driver that wraps the component artifacts and verification floors.

Commands

fiji --version

Print the release version string (e.g. 0.4.0-rc5).

fiji doctor

Diagnose whether the host has a supported Wasmtime. Reports:

• Resolved wasmtime binary path
• Wasmtime major version
• Whether the version is supported by this Fiji release
• Install prefix (where the tarball was extracted)
• Actionable next steps if anything is missing

fiji doctor is the cascading-ladder rule: it only checks for wasmtime and does not depend on wvm or any other runtime manager.

fiji verify-release

Run the release verification floors against the artifacts in this tarball. This exercises the end-to-end path that the release factory recorded as the consumer-visible verification contract.

The release verification contract for the current release is documented in RELEASE_MANIFEST.md.

fiji manifest

Emit MANIFEST.json from the release tarball. This is the machine-readable manifest of every shipped artifact: SHA pins, component identities, version bindings.

fiji wit

Emit the public WIT (fiji:jvm/jvm@0.1.0). This is the contract documented at Public WIT reference and shipped at components/wit/fiji-jvm.wit in the tarball.

Environment variables

Variable	Meaning
FIJI_JDK_IMAGE	Path to the WASI-targeted JDK image used by tutorials and fiji verify-release
FIJI_JVM_OPTIONS	Extra JVM options forwarded to the substrate (e.g. -Dproperty=value)
FIJI_PREFIX	Override the install prefix (used by the installer)

What fiji is not

fiji is not java. It does not invoke javac for you, it does not own classpath assembly, and it does not own runtime configuration beyond release verification. The Fiji runtime is the Wasm component(s) in components/ — fiji is just a consumer-facing driver around them.

If you need direct JVM invocation, drive the component from wasmtime or your preferred component-model host directly. See Hello, Fiji and Same artifact, several runtimes.