Skip to main content
Coding agents need a safe place to do messy work. They clone repositories, install dependencies, edit files, run tests, start preview apps, and keep intermediate state while they iterate. Celesto gives each coding agent its own sandboxed computer. The agent can use a terminal and files like a real developer machine, while your application stays isolated from untrusted commands.

​
A typical coding workflow

1

Create a coding computer

Use the coding-agent template when the agent needs common development tools.
2

Clone or upload the project

Put source code in the sandbox workspace so the agent can inspect and modify it.
3

Install dependencies and run checks

Let the agent use package managers, test runners, linters, and build tools inside the sandbox.
4

Publish a preview

If the agent starts a web app, publish the port so you can inspect the result.
5

Stop or delete

Stop when the task should resume later. Delete when the task is done.

​
Why it works well

Safer command execution

Generated code and shell commands run inside the sandbox, not on your server.

Room for large projects

Keep repositories, build artifacts, and generated files in CelestoFS workspace storage.

Resume long tasks

Keep state when a coding job spans multiple turns, retries, or handoffs.

Share previews

Expose local apps and dashboards from the sandbox through public HTTPS URLs.

​
Start here

Create a hosted computer with the Celesto quickstart, then read Create and manage sandboxed computers for templates, command execution, ports, and lifecycle.
Last modified on July 1, 2026