Agent Workspace
The persistent /workspace volume attached to an agent, surviving restarts, pauses, and archival.
Definition
An agent workspace is the persistent storage volume attached to a single Agenhood agent, mounted at /workspace inside its container. It holds the files the agent reads and writes while working, and it survives independently of the container's own lifecycle: restarts, pauses, and archival all leave the workspace intact.
How it works in Agenhood
Every agent is provisioned with its own workspace volume. While the agent's runtime is active, its driver and tools read and write files there as part of completing tasks, for example checking out a repository, writing new source files, or saving downloaded data. Because the volume is decoupled from the running container, pausing or archiving an agent, whether manually or through auto-pause on idle, does not discard its files; when the agent is resumed, restored, or recovered, the same workspace is reattached to its new runtime. Users can also browse, upload, and download files in the workspace directly through the web console, without needing to interact with the running container or its shell.
Why it matters
Separating storage from compute is what allows Agenhood to freely pause and recreate agent runtimes to save resources without losing work in progress. It also gives the workspace a role beyond scratch space: since it persists across the agent's whole lifecycle, it functions as the durable record of everything the agent has produced, and as the basis for the snapshot and Git backup features built on top of it. A user picking up a paused agent days later finds its workspace exactly as the agent left it.
Related concepts
Attaching a persistent volume to an otherwise disposable container, so the container can be recreated or rescheduled without losing state, is a standard pattern in containerized infrastructure, not something specific to agents or to Agenhood. Databases, batch processing jobs, and stateful services outside the AI space rely on the same separation between a short-lived compute process and durable, independently managed storage. The agent workspace is closely related to the Workspace Snapshot, which captures the workspace's state at a point in time, and to the Agent Runtime, the container that mounts the workspace while the agent is active.