Laptop-bound workflow
Your device or self-managed host holds the state.
This is the right model when local control, offline operation, or specialized hardware matters more than making the task available from elsewhere.
Cloud development environments
What is a cloud coding environment—and when should coding-agent work run in one?
A cloud coding environment is a durable place for the state around a software task to live: its repository, runtime, terminal, browser, and, when supported, its coding-agent session. It lets the work keep its context when the device you use to inspect it changes.
- The workspace is a first-class part of the task
- Changing devices does not require changing hosts
- The environment and the coding agent are separate layers
Start with the state
The important choice is where the work should remain when you step away.
A browser editor alone does not define a cloud development environment. The category is about putting the execution context and the work around it somewhere durable enough to return to: files, runtime, terminal, browser state, and the controls that govern access.
Cloud Environment
The working state stays with the Environment.
The environment becomes the place to re-enter the task, while a phone, tablet, or another computer is simply the client you use to check in.
Make the trade-off explicit
Cloud is a fit for some development work, not every workflow.
Keep work local or self-managed when
The host itself is part of the requirement.
Stay with a machine you operate when the work must run offline, depends on specialized hardware or a private network, or needs a self-hosted setup that you control end to end. A cloud Environment should not erase those constraints from the decision.
Move work to the cloud when
The task needs a durable place to keep running.
A cloud coding environment is useful when a repository task needs an isolated workspace, a real browser, a return path after you leave, or a host that does not depend on keeping a personal computer online.
Cloud development environment vs. local host
Choose the place that should own the task's state.
| Decision question | Local or self-managed host | Cloud coding environment |
|---|---|---|
| Where the working state lives | On your laptop, desktop, or a server you operate. That host remains responsible for availability and recovery. | In a remote Environment that holds the repository, terminal, browser, and supported agent session together. |
| What happens when you change devices | You reconnect to the host or reconstruct the context on another machine. | You return to the Environment from another browser without making a personal computer stay online. |
| Who should choose it | People who need offline work, specialized local hardware, or direct ownership of every part of the host. | People whose task benefits from a durable, isolated workspace and does not need to be tethered to one device. |
| What it is not | Local development is not automatically a problem; it is often the right operational choice. | A cloud Environment is not a promise that every coding agent, credential setup, or self-hosting model is supported. |
Where Sandpi fits
Sandpi is the Environment, not the coding agent.
Sandpi is designed to give supported coding-agent work a durable cloud workspace rather than replace the agent or present itself as a generic cloud IDE. The current public product guidance documents native Codex; support for another harness should be treated as a product fact to verify, not an assumption from this category page.
What stays together
One Environment for the state around substantial work.
- Repository, terminal, and cloud browser in one workspace.
- Environment controls for the network and supported credentials.
- Backups and schedules for work that should outlast a browser tab.
What remains your decision
Choose the agent, access boundary, and operating model deliberately.
A durable environment does not remove the need to decide what a task may access, whether local or self-managed execution is a better fit, or whether a specific coding agent is currently supported for the workflow you need.
Common questions
What to know before moving coding-agent work to the cloud.
What is a cloud coding environment?
It is a cloud-hosted environment for the state around software work: the repository, runtime, terminal, browser, and often a supported coding-agent session. The point is not merely to edit code in a browser, but to have a durable place to return to the same task.
Is a cloud development environment the same as a cloud IDE?
Not necessarily. A cloud IDE is an editor category. A cloud development environment can include an editor, but its core concern is the broader working state: workspace, runtime, terminal, browser, access controls, and the tasks running there.
Does Sandpi replace a coding agent?
No. Sandpi provides the cloud Environment in which supported coding-agent work can run. It does not provide an agent model or turn every agent into a supported integration.
Which coding agents are currently supported?
The current public Sandpi product guidance documents a native Codex connection. Check the current product documentation before choosing a workflow that depends on another coding-agent harness.
When should I keep an agent on my own machine?
Keep the work local or self-managed when offline operation, specialized hardware, direct host ownership, or an existing private infrastructure is the stronger requirement. The right choice is where the task's state should live, not which option sounds more modern.
See the current product