Skip to main content
Connect an agent in one of three ways. Every call it makes through Mirage goes through its mounts, modes and policy.

Coding agents

These run unchanged, on a workspace the mirage CLI creates, whatever language the app is in. These load Mirage as a plugin in place of their own file and shell tools:

Agent SDKs

The app holds the workspace and hands it to the framework. Install the adapter next to the host package, for example pnpm add @struktoai/mirage-vercel @struktoai/mirage-node. When the framework runs in a browser, use @struktoai/mirage-browser in place of @struktoai/mirage-node. Mirage’s seven tools are the session’s session.tools: shell, read, write, edit, ls, grep and glob. A session gets only the ones its profile leaves it, so an agent is never offered a tool whose every call would be refused.

API & Environment

The provider runs the agent, and the workspace is its environment: its own shell and file tools run in Mirage.