Overview

Coding Agents

Claude Code, Codex and Grok Build run as they are, on a workspace the mirage CLI creates, whatever language you build in. Their guides are under Agents.

Agent SDKs

Your program holds the workspace and hands it to the framework.

Framework	Hand it	The agent gets
Claude Agent SDK	`MirageServer(ws)`	Mirage’s seven tools
Agno	`MirageToolkit(ws)`	Mirage’s seven tools
OpenAI Agents	`MirageShellExecutor(ws)`, `MirageEditor(ws)`, `MirageSandboxClient(ws)`	its shell, patch and sandbox tools, run in Mirage
LangChain Deep Agents	`LangchainWorkspace(ws)`	its file and shell tools, run in Mirage
Pydantic AI	`MirageWorkspace(ws)`	its workspace, so every file and shell tool runs in Mirage
Haystack	`MirageShellTool(...)`	a bash tool

Mirage’s seven tools are the session’s session.tools: shell, read, write, edit, ls, grep and glob. A session gets the ones its profile leaves it (session.tools.names()), so an agent is never offered a tool every call of which would be refused. Each framework is an extra: claude-agent-sdk, agno, openai, deepagents or pydantic-ai.

uv add 'mirage-ai[agno]'

Haystack installs as mirage-haystack, which deepset maintains.

API & Environment

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

API	Hand it	The agent gets
OpenAI Agents API	a `self_hosted` environment, through exec-server forward	its shell, file and patch tools, run in Mirage
Claude Managed Agents	`mirage_tools(ws)`, in an `EnvironmentWorker`	its `bash`, `read`, `write`, `edit`, `glob` and `grep`, run in Mirage

Getting Started

Access

AI Agents

VFS

CLIs

Runtimes

Coding Agents

Agent SDKs

API & Environment

​Coding Agents

​Agent SDKs

​API & Environment

Coding Agents

Agent SDKs

API & Environment