Runx is an Apache-2.0 open source runtime built primarily in Rust that executes "agent skill workflows" by treating skills as portable operating manuals (`SKILL.md` files) and composing them into verifiable graphs. It positions itself not as an orchestration framework or vector store, but as a governance layer beneath agents that admits actions under explicit authority, manages credentials without exposing them to prompts, and seals execution results into verifiable receipts. The system enforces strict boundaries where authority narrows through the execution chain, ensuring that deterministic operations, process tools, and agent steps operate within tightly scoped grants.
- The core execution invariant follows a strict pipeline: admit, resolve grant, deliver credentials, execute, and seal.
- Skills are defined by a `SKILL.md` for human-readable knowledge and an optional `run.yaml` for machine-checkable execution contracts and step definitions.
- Credentials are bound to specific environment variables via "connectors," ensuring that the runtime delivers secrets to operations without ever copying them into skill contexts or receipts.
- The project includes a hosted catalog at runx.ai for publishing skills and verifying receipt provenance, though the local CLI can operate independently of any hosted services.
- Recent development focuses on a "hard cutover" to a unified architecture with five distinct step kinds (agent, operation, tool, ask, skill) and a consolidated run record system.
- The core execution invariant follows a strict pipeline: admit, resolve grant, deliver credentials, execute, and seal.
- Skills are defined by a `SKILL.md` for human-readable knowledge and an optional `run.yaml` for machine-checkable execution contracts and step definitions.
- Credentials are bound to specific environment variables via "connectors," ensuring that the runtime delivers secrets to operations without ever copying them into skill contexts or receipts.
- The project includes a hosted catalog at runx.ai for publishing skills and verifying receipt provenance, though the local CLI can operate independently of any hosted services.
- Recent development focuses on a "hard cutover" to a unified architecture with five distinct step kinds (agent, operation, tool, ask, skill) and a consolidated run record system.
