Two ways to set up
With your agent
Paste one prompt into Claude Code, Codex or Cursor. The agent installs the CLI, asks you to approve one browser sign-in, registers the MCP server and proves it works with a sandbox.
By hand, with an API key
Create an
ac_ API key in the console and use it from Python, TypeScript or the CLI.ac_ key you create, which you can scope, expire and revoke.
paste-into-your-agent
Or point the E2B SDK at Anona
The API is compatible with the E2B SDK. Point the stocke2b package at Anona with two environment variables:
setup.sh
api. to the domain itself, so its requests go to https://api.compute.anonalabs.com; that is expected, not a typo.
Then create a sandbox, run a command and watch it:
quickstart.py
Where to go next
Quickstart
Create a sandbox, run a command, clean up.
Migrate from E2B
What carries over unchanged, and what differs.
Recipes
Start from what you are building.
Concepts
Sandboxes, templates, lifecycle, security.
CLI
Lifecycle, exec, ssh, live view and MCP.
API reference
Every route the gateway serves.
What you get
Docs for agents
See Docs for agents.
Pieces
The CLI (npm
@anona-labs/anona-compute) and the Python SDK extras (PyPI anona-compute) are separate packages that share a name: the npm one installs the anona-compute command, the PyPI one is a library and installs no command. Both, and the TypeScript SDK, are open source (Apache-2.0) in anona-compute-sdk.
Anona Compute is in preview. Anything not available yet is marked Coming soon where it appears. Today that is: the CLI’s
keys, limits, push and recover commands, E2B snapshots (create_snapshot), waking a paused sandbox on incoming traffic, and more regions. Anything built but not yet proven in production says so where it matters. Paid plans are paid on the secure Stripe checkout page; see Plans and codes.