Skip to main content
A sandbox is where your agent or automation code runs. Anchor is where the browser runs. The integration Anchor is shipping now is Anchor SDK in the sandbox base image → Anchor Cloud. The sandbox stays vanilla and lightweight. Chromium runs as a managed Anchor cloud session; the sandbox just holds the SDK and talks to it over HTTPS + CDP. Keep those roles separate:
  • The sandbox stays the code runtime — install packages, run a script, call a model.
  • Anchor stays the remote browser — stealth, proxies, live view, and session lifecycle.
  • Connect the two over HTTPS + CDP. Do not launch Chromium inside the sandbox.
This is the same pattern as Stagehand: create an Anchor session, then point your tool at cdp_url when you need full Playwright control.
Anchor’s own Execute Code Snippet tool is different — it runs TypeScript inside an existing Anchor session. Pages in this section attach a sandbox from the outside.

​
What Anchor provides

  • SDKs on npm and PyPI (Playwright or Puppeteer via CDP)
  • Co-branded docs template (MDX)
  • An Agent Skill (SKILL.md) so agents use the tool correctly — bundle it into the partner’s default agent environment or skills catalog
  • Agent Access — a limited keyless trial, not a BYOK replacement

​
Shared setup

Every partner page below uses the same technical contract:
  • Preinstall anchorbrowser in the image (and playwright / playwright-core only if you need direct CDP control).
  • Alias ANCHORBROWSER_API_KEY=${ANCHOR_API_KEY} — the raw SDK reads ANCHORBROWSER_API_KEY. Without that alias, session and task calls fail auth (401) even when ANCHOR_API_KEY is set.
  • Customers bring their own Anchor API key (BYOK). Anchor bills them directly on usage.
  • Prefer agent.task / agentTask for declarative browser work. The result string is result.data.result.
  • Never log session.data.cdp_url — it carries the API key in the query string. Surface session.data.live_view_url to humans instead.
  • Reuse one session per agent run, set timeout.max_duration / timeout.idle_timeout, and delete the session on sandbox teardown.

​
Egress

If the sandbox restricts egress, allowlist:
  • https://api.anchorbrowser.io
  • wss://connect.anchorbrowser.io
  • https://live.anchorbrowser.io

CreateOS

Isolated Linux VMs for agent code, connected to an Anchor cloud browser.

Daytona

Daytona sandboxes as the code runtime, with Anchor as the remote browser.

Tenki

Disposable Linux VMs for agents, connected to an Anchor cloud browser.