Install a plugin you can inspect.

After the quickstart, choose a plugin in the registry. Open its source and documentation before running the install command.

Build, approve, enable.

Run the command from the checkout containing your Torana binary. Use the same TORANA_DATA_DIR as the running server so installation and the control plane see the same state.

./torana plugin install https://github.com/torana-edge/torana-plugins/tree/main/plugins/usage_logger

The command builds and installs the bundle. It does not approve its permissions or enable it. Open http://127.0.0.1:8080/_torana/, review the plugin’s requested capabilities and resource bindings, then approve and enable it. Check that it appears in the active pipeline and send another request.

For the usage logger, the quickstart includes a command to follow the JSONL output. Other plugins may need settings or bound resources first; use their source documentation.

The build is outside the sandbox.

WASM isolates the running guest. That does not make building arbitrary source code safe. In particular, Cargo build scripts can execute native code before there is a WASM artifact to approve. Torana refuses remote Rust source builds; clone and review a Rust project before building it locally.

Why the registry has no published digests.

Torana binds approval to the digest of the locally built WASM artifact. An artifact or permission change requires approval again. The registry lists source rather than promising that every local toolchain will produce identical bytes.

Official Go plugin builds are checked for path independence. That is narrower than reproducibility across every toolchain version. Torana uses GOTOOLCHAIN=local when compiling plugin source, so the source cannot silently select and download another Go toolchain.

The digest identifies what you approved. It is not an independent security review or a reason to skip reading source and permissions.

Turn it off when you’re done.

Disable the plugin in the control plane and save and apply the pipeline change. Verify the active pipeline before continuing. To stop using the proxy entirely, restore your coding agent’s previous provider configuration as described in the quickstart.