Skip to content

Start, save and continue

Open a workspace, bring someone into the task, and keep the work you need.

Open workspace

Your first workspace

  1. Open the tools you needStart from Welcome, or choose a task from Use cases and bring your own files.
  2. Invite someoneUse Participants and invitations. Give them viewing or control-request access, then take turns.
  3. Save before you leaveKeep your private return link. Save or download the work you need; the link alone does not save the computer.

Access, cost and limits

Sign in to launch or join. Keep workspace links private.

A free account is required to launch, join, and use a sandbox. Workspace links carry access permissions; keep your owner link private.

Sandbox creation is free with an account and limited to 10 attempts per account and per IP per hour. Runtime and AI availability depend on deployment limits; external agents may require separate paid credentials. Permanent free access is not promised.

Public workspaces initially expire after 24 hours. Owners can reopen account-linked sandboxes from My sandboxes. Save supported state before expiry; reopening a link does not restore unsaved runtime state.

A link's expiry is separate from workspace retention. A new owner link normally expires after 30 days; invitations can have a different limit. A later link date does not extend the workspace's initial 24-hour retention limit.

External agents may require separate credentials or subscriptions. Keep your private return link; browser history cannot recover it on another device.

Computer environments

Local VM, Cloud and the shared Terminal have different files and saving paths.

Local VM

Linux runs in this browser tab. The shared Terminal runs separately on the server; their files are not automatically synchronized.

Before you start
Requires WebAssembly, workers, browser storage, a configured developer image, and enough device memory. Image download requires a network connection.
Agent access
External CLIs installed in the VM see VM files. Built-in file tools use a separate server agent sandbox. The dedicated run_local_command tool can execute in the VM only with a live human-controller authorization. MCP file tools do not imply VM file access.
When you leave
Closing the host tab stops Local VM execution. Only successfully saved compatible state can be restored; a Git branch is not a machine backup.

Cloud

Linux runs with the configured E2B provider. Cloud Terminal and built-in agent file/command tools use /home/oai/share on that machine.

Before you start
Requires a network connection and a configured Cloud provider. Provider startup may fail even when configuration is present.
Agent access
Built-in file/command tools and installed external CLIs can use this Cloud machine. Credentials and external subscriptions remain separate.
When you leave
The provider may keep work running after tab closure, subject to its timeout. Reconnection and recovery depend on machine availability and saved state.

The shared server Terminal, the server agent sandbox, browser VM files and saved workspace objects are distinct. File access in one does not automatically import or synchronize another.

Try an isolated sample task

A guided practice task, with a manual fallback.

Choose an available Local VM or Cloud starter and open Welcome.

Try the guided sample
  1. PrepareCreate the isolated addition task and reproduce its failing check.
  2. Run and inspectReview the task in Agent, then inspect the actual file and result.
  3. Verify and saveRun the checks. Save supported state before handing off.

Local VM checkpoints and Cloud pause retain different state. A configured agent is not a guarantee of successful execution.

Manual fallback

A guided Terminal task when you cannot run the agent path.

Choose a starter workspace and open Welcome from All Applications. The guided manual task creates a uniquely named fixture in the shared server Terminal environment, reproduces a failing addition check, fixes it and records verification. It uses bundled Node.js without installing dependencies or enabling network access.

This fallback is for an unencrypted Local workspace with an available shared server Terminal. It does not verify the Local VM or an agent. Cloud and agent starter acceptance remain outstanding.

Choose an agent path

Built-in agent, runtime CLI, or a scoped MCP connection.

The built-in hosted agent uses the configured provider and requires current authority. Its ordinary Local file tools use a separate server sandbox; its dedicated Local command tool requires the live controller and running VM. Cloud file and command tools use the Cloud machine. Installed CLI agents receive only the filesystem and credentials available to their process, and do not inherit automatic workspace branching.

For MCP, open Menu → All Applications → Settings → Agent access. Create a scoped credential while holding control; copy it once and keep it private. Start with workspace:read. Revoke from the same screen. Read-only credentials cannot authorize writes or commands.

MCP transport, configuration and troubleshooting. MCP TypeScript SDK 1.30.0 was tested on September 24, 2026 with the server agent filesystem, scoped permissions, control contention and revocation. Other named-client release compatibility remains unverified. Test the documented client/version before relying on it.

Share and hand over control

Invite a viewer, grant control, or send selected evidence.

Open Participants and invitations → Invite a participant. Choose viewing or permission to request control before creating a link. Anyone who has that invitation and any required password can use its access; it is not authenticated membership.

A participant requests control and the current controller can grant it. Releasing control allows a queued eligible participant to continue. When the controller disconnects, the server prefers a queued eligible participant, then another eligible connected participant; otherwise it releases control. Rejoining does not take control back from the current holder.

In Handoff, select recorded evidence, write the decision and exact next step, then preview the packet. Packet-only access lets recipients inspect the selected evidence without joining the live workspace. Workspace invitations are optional and revoked separately.

What each protection means

Control, encryption and rollback cover different things.

Git branch

Tracks committed source changes; does not save machine memory or undo external effects.

Review branch

A separate workspace copy for supported review operations; scope depends on the saved objects and machine state copied.

Checkpoint

A successfully saved supported state, bound to its runtime/image. Unsaved files and external side effects may be outside its scope.

Recorded run

Selected command, output and result evidence. A receipt is not a restorable machine or live workspace.

Workspace rollback cannot undo external messages, purchases or remote-system changes.

Encrypted workspace options

Supported saved object titles/content, encrypted collaborative documents and Local VM snapshots are encrypted in the browser.

Live Terminal traffic, Cloud machine files, AI requests, media, presence and access metadata are separate data paths, outside this saved-content encryption.

The built-in hosted agent cannot use an encrypted workspace. Keep both the workspace link and passphrase; a lost passphrase cannot be recovered.

Save, share and return

Keep your return link and confirm what was saved.

Returning on this device. New workspace links are remembered on this browser when “Remember new workspaces on this device” is enabled on the home page. You can turn it off or forget individual links there. Clearing browser storage removes the list. Keep a private copy of your return link for another device; remembering a link does not save your running machine.

Keeping your work. Check the last successful save before leaving and download files you need to keep. A machine checkpoint, a shared document and a Handoff packet preserve different things. Retry a failed save; keep the last good checkpoint. A browser exit prompt cannot prevent every crash.

A link's expiry is separate from workspace retention. Public workspaces have an initial 24-hour retention limit. Access links normally expire after 30 days, unless a different limit is set. Replacing a link does not extend workspace retention; an expired or revoked link does not itself mean the workspace was deleted.

If a link stops working. Check the full address or try a newer saved link. If someone invited you, ask them for a new invitation. Owners can reopen account-linked workspaces from My sandboxes after signing in. A lost passphrase still requires a previously saved recovery code.

Sharing access. Use invitation controls to choose the recipient's access. Anyone with the link and any required password can use it. A Handoff packet shares selected evidence; machine access requires a separate invitation.

Sandbox creation is free with an account and limited to 10 attempts per account and per IP per hour. Runtime and AI availability depend on deployment limits; external agents may require separate paid credentials. Permanent free access is not promised.

Contact and privacy support

Files and saved state

Each environment has its own filesystem and recovery scope.

In Files, choose Shared Terminal to browse and download files created by server Terminal commands. Local VM opens files inside the browser computer; Documents contains workspace documents; Received contains files sent to this device. Each location keeps its own files. The hosted agent sandbox is separate. Cloud Terminal and built-in Cloud tools share /home/oai/share.

Use the existing download action for a captured run artifact or a received file. Opening a guest file creates the supported workspace view; it does not make every workspace document a guest file. The Files app does not currently import an arbitrary repository into Cloud or synchronize these environments.

“Save on this device” stores VM state and image identity atomically in this browser. It is not shared with teammates. A compatible server checkpoint takes priority on reopening; unknown image identities are preserved but cannot be booted automatically. A Handoff packet stores selected evidence, not the VM itself.