Run the full test suite remotely.
Using opencloudbox…Remote computers for coding agents.
One command
is all it takes.
Start a remote computer in one command. Keep using your local coding agents and existing subscriptions, sync your project, and run the work remotely. Use the managed provider or bring your own supported sandbox provider through the local CLI.
ocbox startTechnical preview
Your agent stays yours—your subscription, your keys. We give it a computer of its own.
Your agent stays here.
The work runs there.
opencloudbox is not another agent. It gives the coding agent already on your machine a separate computer for selected work.
$ npm test
✓ unit 24 passed
✓ integration 8 passed
✓ build complete
exit 0
Use it from wherever
the work begins.
The CLI and hosted MCP are equal entry points. The web app keeps the same Projects and Sessions visible without becoming a separate workflow.
~/work/opencloudboxzsh · local
$ ocbox start
Project opencloudbox.dev
Sync 148 files uploaded · exclusions applied
Provider opencloudbox
Session s_9c2a ready
$ ocbox exec npm test
All checks passed
exit 0 · 18.4s
Choose who supplies
the computer.
Projects and Sessions behave the same either way. What changes is the infrastructure relationship.
We supply it.
Starts withYour opencloudbox account
Routes throughopencloudbox control plane
Runs onManaged remote computerRemote Session
The provider is the compute boundary.
Agent output, repository code, dependencies, and Session processes are untrusted by default. In bring-your-own-provider mode, the provider credential remains on your device.
Read the complete boundary modelStays localAgent · editor · subscription · provider key
Runs remotelySelected files · commands · processes
Keep your agent.
Give it a computer
of its own.
ocbox start