Patterns that need continuity
Large coding tasks
Keep dependencies, build output, edited files, and test results across retries.
Browser investigations
Save reports, screenshots, downloaded files, and intermediate notes.
Large artifacts
Store generated data, datasets, logs, and project files in CelestoFS.
Human handoffs
Resume the same computer after review, approval, or a later background job.
Lifecycle rule of thumb
| Action | Use when | Result |
|---|---|---|
| Stop | The task should continue later. | The computer turns off and keeps saved state. |
| Start | The agent is ready to continue. | The same computer comes back with saved files and state. |
| Delete | The task is finished. | The computer and saved state are removed. |
Design your job record
For long-running workflows, store the Celesto computer ID or name alongside your own job record. That lets a worker, agent, or human-triggered resume step return to the same computer later.Lifecycle guide
Learn create, stop, start, resume, and delete behavior.
Persistent state
Keep files, installed packages, and workspace changes between sessions.