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.
For Codex work that outlasts a device
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.

Make the right trade-off
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
The task remains anchored to the computer or server you manage, along with the access and availability that machine needs.
Sandpi Environment
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
Reopening Sandpi is not an invitation to reconstruct the context. It is a way back to the same task and the state around it.
Sandpi Environment
The work stays here.Start a new Environment or return to the one already holding your task.

When the task needs a real browser
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.
Keep control with the work
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.

Where this changes the workday
Start a substantial task on a laptop, check in from a phone, and return to the same working state later.
Reproduce an issue in a shared cloud browser, complete a login yourself, then let Codex inspect that same state.
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
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.
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.
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