Environments
Each Spinup Agent runs inside its own isolated environment. The environment is runtime capacity, not the agent itself.
Every Spinup Agent runs inside its own isolated environment. The environment is the computer-like runtime Spinup provisions for the agent: filesystem, packages, tools, the installed harness, projected secrets, network policy, and lifecycle behavior.
The environment is runtime capacity. It is not the agent.
What belongs to the environment
The environment holds the things a harness needs to run right now:
- the filesystem and any installed packages
- the harness binaries and their on-disk state
- secrets projected for the current run
- temporary files and working state
- the network policy in force
When the environment is replaced, these are rebuilt from the agent's settings. Nothing important is lost because nothing important lived only here.
Lifecycle
Spinup can update, replace, or stop an environment while preserving the agent. Updates pick up new capability settings or harness choices. Replacements move the agent onto fresh runtime capacity without changing what you configured.
Sleep and wake will let an environment stand down between runs and come back when the next request arrives. That capability is on the roadmap; not shipped yet.
Where to go next
- See Spinup Agents for what survives across environments.
- See Harnesses for the engine that runs inside the environment.
- See Runs for what happens when a request lands.
- Check environment readiness through Status and exec.
- Inspect environment status from the workspace API with Control plane agents.
Spinup Agents
The durable product object you configure and run. Memory, capabilities, secrets, harness choices, and run history live with the agent, above any one runtime environment.
Harnesses
The engine that runs inside the environment. The same Spinup Agent can be projected into different harnesses without losing memory, skills, or secrets.