agentic-runner
The Agentic OS Runner (ADR-0013): an activity-only Temporal worker that executes
exactly what must happen where the workspace, the Agent Runtime subprocess, a verb seam
or a credential the Runner holds is. The Ralph Loop — every @workflow.defn — runs on
platform-hosted Platform Workers and never ships here.
It depends on agentic-runner-contracts and third-party packages only: it imports no
platform module, enforced by tests/test_package_partition.py.
Without the platform — its namespace, Directive tokens, Grant snapshots, Evidence sink and the loop itself — this package is an executor with no scheduler, no governance and no intake. That inertness, not obfuscation, is the boundary (ADR-0013 §5).
Running it
agentic-runner run is the process: it exchanges the Runner Registration Token in
AGENTIC_RUNNER_REGISTRATION_TOKEN (or, deprecated, AGENTIC_AGENT_TOKEN) for a durable
identity at AGENTIC_CONTROL_PLANE_URL (once, persisted under AGENTIC_RUNNER_STATE_DIR),
heartbeats every 30 s, connects to the
namespace it was handed with the Runner Token the heartbeat refreshes, and polls its own
runner.{runner_id} queue. AGENTIC_RUNNER_ISOLATION is contract_uid (default: every
Contract its own uid, needs CAP_SETUID — refused otherwise) or none. Readiness is
GET /healthz on AGENTIC_RUNNER_READINESS_PORT.
It ships as ghcr.io/qtsone/agentic-runner (Dockerfile.runner at the repository
root: Python, git, codex, claude, nothing else) and installs with
charts/agentic-runner.
On a workstation it is a per-user login agent, one per Runner:
agentic-runner install | start | stop | status <name> and agentic-runner list
(LaunchAgent, systemd user unit or logon task; never sudo), with Credential References in
the OS credential store.
Licensed under AGPL-3.0-only.
1 maintainer
Metadata
1 maintainer
Release files for agentic-runner 4.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentic_runner-4.1.0.tar.gz | 364.8 kB | With provenance | Details for agentic_runner-4.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentic_runner-4.1.0-py3-none-any.whl | Python 3 | none | any | Details for agentic_runner-4.1.0-py3-none-any.whl |
Total release size: 778.5 kB
Release files / agentic_runner-4.1.0.tar.gz
| Download URL | agentic_runner-4.1.0.tar.gz |
|---|---|
| Size | 364.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea18297f93e7ffff00edc82327591d4bb0c60b34566e6b578c2becae94d532a6
|
|
BLAKE2b-256 checksum How to use checksums |
799255ea868c11d529cc3dea70b4e8043c6a841c437859e90a7ac03f69307aa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / agentic_runner-4.1.0-py3-none-any.whl
| Download URL | agentic_runner-4.1.0-py3-none-any.whl |
|---|---|
| Size | 413.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6db062068ea79f0515b8248ab4405bc63f081db02f601d4226a03d7d0dcf77a
|
|
BLAKE2b-256 checksum How to use checksums |
e124d5e408d08bd34836dcc5676b5dfb6cc82ab8d0228159d9af097117a80faa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for agentic-runner 4.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agentic_runner-4.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
