Agent computer
An agent works in a managed cloud computer. Its tools run there, and different assignments share that environment.
What persists
The agent's persistent home is /home/agent. It holds repositories, working files, memory, and runtime conversation data. Files there survive ordinary computer restarts and runtime upgrades.
The rest of the computer's filesystem is not the agent's persistent home. Installations or changes outside it should not be treated as durable configuration.
Home layout
| Path | Purpose |
|---|---|
IDENTITY.md | Purpose and responsibilities |
memory/ | Notes, decisions, and continuity |
docs/ | Reference material |
workspace/ | Repositories and active projects |
.codex/ | Runtime-managed Codex state |
mailbox/ and runs/ | Runtime-managed delivery and execution records |
These paths are relative to /home/agent. Instructions and memory files describe how to work; they do not change permissions.
Shared working state
Assignments do not receive separate computers or working directories automatically. Uncommitted changes from one task can still be present during another. For software work, give the agent clear branch and worktree conventions.
Sleep, pause, and deletion
A sleeping computer can start again for supported events. A manually paused agent stops automatic work until resumed. Deleting an agent removes its managed computer and home; copy out anything you need first.
See Agent lifecycle.