The cloud development environment where AI coding agents keep running
Every project gets a persistent, isolated container with the agents already installed. Close your laptop and reconnect to the same session from any device.
The agent workspace that survives your laptop
CloudCLI keeps the infrastructure close to the coding workflow: one container per project, agents ready, and the same session available wherever you reconnect.
Persistent container per project
It does not stop when your laptop sleeps.
Per-developer isolation
Your environment is yours alone, not a shared box.
Agents pre-installed
Claude Code, Cursor CLI, Codex, and Gemini CLI are ready. Bring your own keys.
Reach it from any screen
Phone, browser, VS Code, or SSH. Same session, same workspace.
How an environment is provisioned
Connect a repo. Pick a tier. CloudCLI creates a persistent container with the workspace, shell, and agent surface ready together.
Create the environment from a repo
Connect a repository, pick the Starter tier, and create a persistent workspace without SSH tunnels, tmux setup, or local machine babysitting.
Land in a real running workspace
The running environment brings the file tree, terminal, and Claude Code agent panel into one persistent container. The session stays available when you reconnect from another device.
What changes when the environment runs in the cloud
The value is not a remote editor. It is a persistent machine where agents, credentials, files, and terminal state survive the places your laptop cannot.
A real machine, priced plainly
Starter gives each environment 2 CPU cores and 4 GB RAM for EUR 7/month. The workspace runs as a container, not a toy sandbox.
Long jobs keep running
Kick off tests, refactors, or migrations, close the laptop, and reconnect later to the same running workspace.
Your code and keys stay isolated
Each developer gets a separate Docker container. Credentials are encrypted and forwarded to agents without becoming shared team state.
FAQ
A cloud development environment (CDE) is a containerized workspace that runs on remote infrastructure instead of your local machine. With CloudCLI, that container has your AI coding agents pre-installed, a file explorer, a Git UI, and a shell, and it persists between sessions.
A local environment lives on your machine and stops when the machine sleeps or changes. A CloudCLI environment runs in the cloud, so it survives a closed laptop, a dropped network, and a device switch.
Yes. The agent runs inside the cloud container, not on your laptop. Close the lid and the agent keeps working. Long jobs finish while you are away, and the result is waiting when you reconnect.
Yes. Every developer gets their own Docker container with encrypted credentials. Environments are isolated from each other even when a team shares MCP servers and configuration.
Give your agents a home that persists
Create a cloud environment where the workspace, shell, files, and agent session stay available between devices.