Runtime Configuration
The runtime exposes both process-level configuration and claim-time execution contracts from the platform.
That distinction matters. Some runtime behavior is configured when the service boots. Other behavior is delivered per task by the control plane.
Checked-In Runtime Config
Section titled “Checked-In Runtime Config”The example file in
agirunner-runtime/configs/runtime-config.example.yaml covers basic
process concerns such as:
- connection details for the platform
- worker or runtime identity
- health and observability endpoints
- provider wiring and local process defaults
What Operators Should Remember
Section titled “What Operators Should Remember”Boot-time runtime config is not the same thing as workflow policy. Playbook meaning, role assignments, tool grants, and execution contracts still come from the platform.
Why It Matters
Section titled “Why It Matters”Thinking about configuration this way keeps the runtime focused on execution concerns instead of smuggling workflow semantics into local process settings.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Runtime configuration is only one layer of the full operating model:
- Agentic Settings and Platform Settings are the dashboard surfaces where operators shape many runtime-facing defaults
- Runtime Operations explains how those settings relate to the runtime service as a whole
- API Reference covers the platform-side registration and fleet contracts the runtime uses after boot
This page answers “how does the runtime process start and connect?” The dashboard and API pages answer “what policy and execution contracts does the platform hand it once it is running?”