Extensions
Extensions add Console screens, API routes and background logic to a project. An extension receives only the permissions its manifest declares and the project admin approves.
An extension runs in an isolated sandbox with no network of its own, so everything it does passes through points the platform controls:
- Ingress. A call to an extension enters the platform here.
- The extension. Your code runs in a Firelock sandbox on Bun or Wasmtime. The sandbox has no network of its own. Everything the extension sends out leaves through one auditable channel.
- Decision Oracle. Warden, the Decision Oracle, evaluates every call the extension makes. External agents that submit tool calls through the platform's MCP interface meet the same checks.
- Human review. When a call needs a person's approval, the Decision Oracle escalates it to a human reviewer.
- Credentials Oracle. A call the Decision Oracle allows goes to the Credentials Oracle, which brokers every credential the call needs.
- Kibo. The Credentials Oracle works with Kibo, which holds the credentials. The extension never holds a credential.
- Egress. The call leaves the platform here, and only to endpoints on an allow-list.
The extensions Kilimanjaro builds are Paperless, Context, Lookout and Gate Studio. Third-party extensions install through the same contract. To build one, see Build your own extension.