For Codex work that outlasts a device

Your Codex task stays put. You don't have to.

Start a real task on your laptop. Step away, check in from a phone or tablet, and return to the same repository, terminal, browser, and native Codex session—without leaving a computer online.

Open the app to start or return to an Environment.

  • Same native Codex session
  • Same repository, terminal, and browser
  • No computer to keep online
Sandpi workspace showing a Codex conversation, file tree, Git status, and code editor.
The conversation, files, Git state, and editor persist in one Environment.

Make the right trade-off

Keep the work in the cloud, not tethered to a machine.

Remote control lets you reach a computer or server you operate. Sandpi gives a native Codex task a durable cloud Environment, so the work itself has somewhere to stay when you move.

Remote control

Reach the computer. Keep the computer running.

The task remains anchored to the computer or server you manage, along with the access and availability that machine needs.

Sandpi Environment

Open the same task. The Environment stays available.

The native Codex session, repository, terminal, and browser live together in an isolated cloud workspace instead of on the device you happened to start with.

What the handoff looks like

Leave the desk without resetting the task.

Reopening Sandpi is not an invitation to reconstruct the context. It is a way back to the same task and the state around it.

Start onYour laptop

Sandpi Environment

The work stays here.
  • Native Codex session
  • Repository and terminal
  • Shared browser
Continue onPhone, tablet, or desktop
Open Sandpi

Start a new Environment or return to the one already holding your task.

Sandpi's shared browser showing a local app inside a Codex workspace.
Use the same cloud browser session to inspect the app with Codex.

When the task needs a real browser

Look at the same browser Codex can use.

Some failures only make sense with a running app, a real browser, and an authenticated state. Sandpi gives you and Codex one shared Playwright browser inside the Environment instead of asking you to recreate that context on another machine.

  • Inspect a live tab and application state from the Environment.
  • Complete an interactive login yourself, then hand that browser back.
  • Check desktop, responsive, and mobile viewports in one place.

Keep control with the work

Put the task in a boundary you can leave running.

An Environment gives a task an isolated runtime and controls that match it. Configure outbound access and supported credential injection at that boundary, protect the Workspace with backups, and schedule work that should happen later.

  • Keep supported credentials out of the repository and browser.
  • Use manual or scheduled Workspace backups with restore controls.
  • Run a Codex prompt once or on a recurring schedule with run history.
Sandpi Environment settings showing sandbox controls and workspace backups.
Environment settings keep runtime, backup, network, and agent controls together.

Where this changes the workday

For the moments a laptop-bound workflow breaks.

01

Step away without restarting the job

Start a substantial task on a laptop, check in from a phone, and return to the same working state later.

02

Debug the state that needs a real browser

Reproduce an issue in a shared cloud browser, complete a login yourself, then let Codex inspect that same state.

03

Leave recurring maintenance somewhere durable

Schedule a Codex prompt once or on a recurrence, then return to its run history in the Environment instead of relying on an open tab.

Answer the decision questions

What to know before moving a task into Sandpi.

Does Sandpi replace Codex?

No. Sandpi is designed to run the native coding-agent experience in a durable remote Environment. Codex is the currently implemented harness, so the product is for people who want a longer-lived place for their Codex work to run.

Is Sandpi a remote desktop?

No. Remote-control tools extend access to a computer or server you operate. Sandpi runs the workspace, terminal, browser, and native Codex session together in a cloud sandbox, so your local computer does not need to remain online for the task to stay available.

What happens to credentials and project access?

Configure each Environment's network policy and supported credential bindings at the boundary instead of placing secrets in the repository. An agent can still use any destination or credential explicitly granted to its Environment, so those grants remain part of the security decision.

Ready when the work is

Start the next substantial Codex task in an Environment that stays available.

Open Sandpi