box gives your AI agent a computer of its own: a cloud Linux desktop with Chrome and a shell that it drives over MCP, while your own computer stays free. You can watch it live and take over at https://box.simular.ai/box.
Most agents need no plugin: add the MCP server https://mcp.box.simular.ai/mcp and sign in once (see https://box.simular.ai/install). This repository holds a package for each agent that installs box its own way. Each folder stands alone and is released through that agent's channel.
| Agent | Folder | Sign-in | Install |
|---|---|---|---|
| Claude Code and Cowork | claude/ |
OAuth, once in the browser | /plugin marketplace add simular-ai/box-plugin, then /plugin install box@simular-box |
| DeepSeek Harness (dsh) | dsh/ |
Personal key (cb_...), pasted on the plugin's page in Plugins |
dsh/README.md |
| Any of Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Hermes, OpenClaw, VS Code (and steps for Claude Desktop) | cli/ |
OAuth; personal key with --auth key for Hermes and OpenClaw |
npx @simular-ai/box connect (check with npx @simular-ai/box doctor) |
| Hermes Agent | hermes/ |
Personal key (cb_...) in MCP_BOX_API_KEY; OAuth optional |
hermes/README.md |
Going offline in the middle of a task? In Claude Code with the plugin, /box:offload hands the task to a fresh Claude Code (or Codex, Cursor) session in your box, which keeps working while you are away; /box:back brings its commits and its written hand-over home and merges them. Any other agent or a plain terminal uses npx @simular-ai/box offload and npx @simular-ai/box back. Setup and details: cli/README.md.
Add a folder named after the agent with its own manifest, MCP config and, where the agent supports skills, a copy of claude/skills/box/SKILL.md. Point it at https://mcp.box.simular.ai/mcp. Use OAuth sign-in where the agent supports it; otherwise read a personal key from an environment variable or the agent's own credentials store, never from a file in the package. Add a row above.
claude/: bumpversioninclaude/.claude-plugin/plugin.json. Claude Code doesn't auto-update third-party marketplaces: users get it with/plugin marketplace update simular-boxand/plugin update box@simular-box, or withnpx @simular-ai/box connect.dsh/: bumpversionindsh/package.json, then push a tagdsh-vX.Y.Z. The release workflow attachesdsh-box.tgz.hermes/: bumpversioninhermes/plugin.json. Users copy the folder by hand until box is in the Hermes plugin catalog.cli/: bumpversionincli/package.json, then push a tagcli-vX.Y.Z. Thepublish-cli.ymlworkflow tests it and publishes@simular-ai/boxto npm through trusted publishing (OIDC), with provenance; the one-time npm setup is in cli/README.md. When the box endpoint moves, changeDEFAULT_MCP_URLincli/src/constants.js, add the old host toOLD_HOSTSthere, change the URL in every plugin folder, and release each one.