Environments
The Environments page manages the execution-environment records used by specialist roles.
This page is important because it shows that Agirunner separates the long-running runtime service from the task execution environment. The runtime hosts the loop and platform connection. The environment record describes where specialist work actually runs.
What Lives Here
Section titled “What Lives Here”- configured execution environment records
- image reference, pull policy, CPU, and memory posture
- catalog-backed environment creation
- verification, archive, restore, and default selection flows
Why It Matters
Section titled “Why It Matters”This is the operator surface for the environment where specialist tasks actually run. It is distinct from the lightweight runtime image that hosts the agent loop. In practice, the orchestrator and specialist agent loops ride in a lightweight Alpine-based runtime image, while the heavier language runtimes, package managers, and system libraries live in the execution environments selected here. That separation is one of the clearest pieces of Agirunner’s execution model.
Built-In Starter Environments
Section titled “Built-In Starter Environments”Fresh tenants are seeded with a built-in starter catalog so operators do not begin from a blank slate.
Current starter environments include:
- Debian Base, which is also the default seeded environment
- Ubuntu LTS Base
- Alpine Base
- Fedora Base
- Python Base
- Node LTS Base
- Go Base
- Rust Base
- Java Base
- PHP Base
These are starter images, not a frozen long-term support matrix. The catalog gives operators a fast path to common execution postures, and the platform can verify or replace them later with custom images as teams learn what their work actually needs.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Environment records only become meaningful when they are attached to the rest of the execution path:
- Specialists, Skills, And Models is where a specialist role is linked to an execution environment
- Workflows and Workflow Detail are where you see the consequences of that choice during real work
- Runtime Operations and Live Containers are where you verify the runtime is actually launching work with the expected execution posture
In practice, the environment page answers “what execution profiles exist?”, while the specialist page answers “who uses which one?” and the workflow/runtime surfaces answer “how did that choice behave under load?”
Operator Use
Section titled “Operator Use”Use this page when you need to:
- create a new execution image profile
- make one environment the default for new roles
- verify that an environment record is healthy before using it broadly
- archive older environments without losing their history