Workspace instead of the host. The agent’s shell, file reads/writes, and search all run inside Mirage; mount RAM, S3, GDrive, Slack, etc. and the agent uses them through the same camel API.
Install
camel-ai>=0.2.40,<0.3 and markitdown>=0.1.5. Note: mirage-ai[camel] is mutually exclusive with [openai], [openhands], and [pydantic-ai], camel pins pydantic<=2.12.0 while the other agent SDKs require >=2.12.2. Pick one stack per environment.
Usage
Toolkits
MirageTerminalToolkit
Drop-in replacement for camel’s TerminalToolkit. Same 6 functions, all routed through Workspace.execute():
No docker backend, no env-cloning, no safe-mode allowlist. Mirage Workspace already isolates execution.
MirageFileToolkit
Subclasses camel’s FileToolkit, inherits all 7 public methods and every format writer (PDF, DOCX, JSON, CSV, HTML, ipynb, plain text). Path resolution and IO are overridden to route through Mirage; format writers operate on a tempfile and the result is pushed via Workspace.execute(f"cat > {path}", stdin=...).
Exports
Examples
examples/python/agents/camel/sandbox_agent.py,ChatAgentwith both toolkits over a RAM workspace.