Package availability (former Serve reference)

Executable extension bundles are pinned to the host version. The 0.10.2 catalog includes six optional bundles, including Pi. Older bundles need their matching host; do not reuse a 0.9.6 bundle with octet 0.10.2.

octet extension install octet-web-search
octet extension list

For a reviewed local archive instead, use octet extension install --path ./bundle.tar.gz. Installing is inert: it doesn't enable a package, save a trust grant, start code or set up dependencies. Full access implicitly trusts selected executable extensions, but enabling stays explicit. Safe mode starts only enabled extensions with host authority for their selected source; ungranted sources stay stopped. --trust-extension, an explicit --extension-dir, or a source-bound trusted_extensions grant can supply that authority, but never enables a bundle. --no-process/--no-shell, workspace trust, and compatibility/integrity checks still apply. Granted code runs with your OS permissions outside the tool-effect broker: safe mode is not an OS sandbox. Executable bundles are separate from the terminal binary. Resource discovery covers source selection, and extensions covers packaging, trust, atomic update and removal. Catalog install and update select the package that matches the running octet version. The command forms are in the CLI reference.

Package	What it adds
`octet-web-search`	Public web search and fetch, via Brave Search (recommended) or SearXNG. Not a browser.
`octet-computer-use`	Native desktop control (macOS, Windows, Linux) through a locally installed, MIT-licensed Cua Driver. Provisioning is explicit, and the OS permissions are yours to grant.
`octet-codemode`	Pi's offline JavaScript tool composition, one Rust executable with the embedded QuickJS/WASM engine; no Node.js or Python is required. Explicitly enabled tools retain normal host policy and budgets.
`octet-mcp`	An MCP bridge. Local stdio works. Remote Streamable HTTP is blocked by default.
`octet-subagents`	Bounded workers. Enabling is explicit, and full-access trust follows host policy.
`octet-pi-compat`	Pi 1.0.2 compatibility adapter. Enabling the stock bridge automatically mirrors and executes enabled Pi factories with OS permissions; not blanket parity.

The six executable-bundle manifests declare API 0.4, distribution version 0.10.2, and require octet =0.10.2. Older bundles stay pinned to their host. Distribution and host versions are independent boundaries, and an API number doesn't bypass the exact host pin. See current authoring for the Python API 0.4 process recipe and the retained API 0.3 conformance example. Generated contract bindings alone aren't a process runtime. Pi installation and discovery are inert; separate enablement of the stock bridge automatically mirrors/runs enabled Pi factories. It does not silently opt into native provider credential disclosure. Native TOML appearance remains independent; the 27-row ledger retains partial contracts. Previously installed experimental copies are not automatically removed.

Python-script adapters need Python >=3.11 with venv and ensurepip, or explicit private-runtime setup; this is not a prerequisite for every native Octet launch. Pi needs Node >=22.19.0; Codemode needs neither Python nor Node at runtime.