Verdog runtime
Execute Verdog workflows in Python. The runtime runs workflow steps and configured agents, records execution history, and supports resuming or forking runs from compatible checkpoints.
Requires Python 3.12 or later.
Installation
Generated workflow projects declare verdog-runtime as a dependency. To install
it directly in a Python environment:
uv pip install verdog-runtime
For creating, checking, and running projects from the terminal, install the Verdog CLI:
uv tool install verdog-cli
verdog --help
Workflow environments need the runtime and their declared dependencies. They do not require the CLI or a backend installation to execute workflows.
Documentation
- Getting started
- Running example
- Workflow declarations
- Interpreter reference
- Execution logs and statistics
Runtime 0.1.9 adds the opt-in CodexInvoker(danger_full_access=True) for
hosts where Codex's sandbox cannot start, records each invocation's effective
sandbox in metadata.json, and counts Codex error items as failed tool calls.
Runtime 0.1.6 stores checkpoint artifact inventories as add-only deltas and shares their ancestry in memory. Existing full-inventory checkpoints remain readable; existing run files are not rewritten.
Runtime 0.1.5 extends each stats.md timing table with agent call
counts, input and cached input tokens, output tokens, and estimated USD usage
cost. Child usage rolls into its parent call row; parent and previous/next call
links keep the existing report hierarchy navigable. Subscription cost estimates
describe usage, not additional charges or remaining quota. Token and cost cells
use — for Python, Feature, enter, exit, and failure rows where usage does not
apply. Agent, Subroutine call, Workflow call, and Total rows use 0 for no
usage, unknown for missing measurements, and a known subtotal followed by
+ ? for partial measurements. Agent call counts are always numeric.
Development
See developer documentation for setup, checks, run-monitoring APIs, and release instructions.
License
AGPL-3.0-only; see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for verdog-runtime 0.1.9
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 |
|---|---|---|---|---|
| verdog_runtime-0.1.9.tar.gz | 259.2 kB | With provenance | Details for verdog_runtime-0.1.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| verdog_runtime-0.1.9-py3-none-any.whl | Python 3 | none | any | Details for verdog_runtime-0.1.9-py3-none-any.whl |
Total release size: 427.7 kB
Release files / verdog_runtime-0.1.9.tar.gz
| Download URL | verdog_runtime-0.1.9.tar.gz |
|---|---|
| Size | 259.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3886d9f8e6dcc037cc75cffce9c308fb2f7b91494f440854b357386ebe13679
|
|
BLAKE2b-256 checksum How to use checksums |
0538af6204061c03f09495c3c72fd5c914f2cae7e7a88480dc3bfc706347fc89
|
| 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 1, 2026.
Transparency logRelease files / verdog_runtime-0.1.9-py3-none-any.whl
| Download URL | verdog_runtime-0.1.9-py3-none-any.whl |
|---|---|
| Size | 168.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d30a8ef9608808bd6dd7e16938da81a7603591c228f5ea8ee8d798be1853398d
|
|
BLAKE2b-256 checksum How to use checksums |
e90abb6846499c7b84301c93de5c44c3c9d8a0ea6a81c50fb68abe3f44837334
|
| 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 1, 2026.
Transparency logSecurity for verdog-runtime 0.1.9
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
Both files in this release have been uploaded with provenance metadata.
Attestation for verdog_runtime-0.1.9.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 1, 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.
