Chrome Sandbox · Cloud browser for AI agents
A cloud browser
for every
agent session.
Keep Codex or Claude Code on your machine. Give each session its own Chrome and desktop in the cloud. Work in parallel, then step into the same browser whenever you need to.
Separate sandboxes across sessions.
A shared browser for you and your agent within each one.
Research brief
01 / 03Move this session forward. Switch sessions to see that their progress stays separate.
Illustration. Create a sandbox in Console to use a real cloud browser.
Independent browser sessions
Chrome + a full desktop
Persistent profiles and files
Human and agent access
01Parallel work, separate environments
Let every session
keep its own place.
A research task, a browser test and an operations workflow can each have their own Chrome sandbox. Choose exactly which environment your agent uses.
Keep tasks independent
Give concurrent sessions separate browser processes, profiles, desktops and files. One session can navigate or restart its Chrome without taking over another session’s browser.
Step in when the agent needs you
Open the private viewer to sign in, inspect a page or take the next action. You and the agent see the same browser and login state. Coordinate before navigating or typing.
Return to a prepared environment
Keep saved profile data, downloads and installed tools with the sandbox’s writable filesystem. Pause compute between tasks and return to the same environment when you need it.
02Bring your coding agent
From a local session
to a cloud browser.
- 01 / PROVISION
Create a Chrome sandbox
Choose the chrome template in Console. Create a separate sandbox for each session you want to run in parallel.
- 02 / OPEN
Open your browser
Click Open browser. The startup page opens your private Chrome desktop when it is ready. Sign in to the sites your task needs.
- 03 / CONNECT
Connect your agent
Click Connect agent in the viewer and paste the prompt into Codex, Claude Code or your coding agent. Configure Sandbox0 authentication locally.
Your agent stays in your existing workflow. The Chrome template includes the browser, desktop and Playwright CLI; it does not require you to move your coding-agent harness into the sandbox.
03A browser with a whole computer behind it
Keep the desktop,
the downloads,
and the setup.
Use Chrome in its full desktop, work with downloaded files and install the tools your task needs. The sandbox preserves the whole writable filesystem across successful checkpoints.
Explore persistence and on-demand computeInside each Chrome sandbox
Chrome
Your tabs and profile
Desktop
A private, visible workspace
Files
Downloads and installed tools
Agent access
Playwright in the same sandbox
Default pause/resume restarts processes. Saved profile files and downloads persist; live tabs and in-flight browser actions are not guaranteed.
View pricing04Questions
Cloud browser,
explained.
What is a cloud browser?
A cloud browser runs on a remote computer and can be controlled from your device or by software. Sandbox0 gives you headed Chrome, a full desktop and a private web viewer inside a persistent sandbox. Your coding agent can operate that same browser through authenticated Sandbox0 tooling.
Can I use my local Codex or Claude Code?
Yes. Create a Chrome sandbox, click Open browser, then use Connect agent in the viewer. Copy the prompt into your local coding agent and configure its Sandbox0 credentials locally. The agent runs Playwright CLI inside the sandbox and attaches to the existing Chrome browser. Each parallel agent session should use a separate sandbox.
Do I need a separate sandbox just to isolate cookies?
Browser contexts or separate local Chrome profiles can be enough for cookie isolation. A Chrome sandbox also gives each session its own browser processes, desktop, files and tools in the cloud. Use it when you want to manage the whole environment and let a human access the same browser.
What persists when I pause the cloud browser?
Committed browser profile files and downloads persist with the sandbox filesystem. Websites can still expire their login sessions. Default pause/resume starts fresh processes; live tabs and in-flight page state are not guaranteed. Reopen the viewer and reconnect the agent after resume.
Does it use my laptop's existing Chrome logins?
The cloud browser has its own profile. Sign in through the private viewer, then let your agent continue in that same cloud browser. It does not automatically copy your laptop's cookies. Coordinate human and agent actions when sharing a session.
Can it open an app running on localhost?
Chrome can open development servers running inside the same sandbox. In the cloud browser, localhost refers to the sandbox. To test an app running on your laptop, provide a reachable preview URL or run the app in the sandbox.
One cloud browser for each session
Give your next task its own Chrome.
Bring your agent. Open the desktop. Keep the work.