
ReadyAgents
io.github.readyagentsdevPublished by GitHub account readyagentsdevv2.0.12Updated Oct 24, 2026
Local YAML/JSON agent workflow CLI with approvals, resume, and optional stdio or loopback MCP HTTP.
Overview
Local CLI that runs YAML/JSON agent workflows with checkpointing, human approvals and resume, and can expose builtin tools as a stdio MCP server.
- What you can do
- Author and run agent workflows: define YAML/JSON graphs with agent, tool, condition, transform, approval, parallel, foreach and decide nodes, and scaffold starters from templates or shipped examples.
- Run and resume runs: persist state after every node, pause for human approval, resume or replay a run, and inspect, fork, diff or freeze past runs.
- Use builtin tools without extra servers: now, calc, json_get, list_dir, read_file and write_file.
- Govern cost and policy: spend ledger, per-node token/cost, estimate and max-spend caps, model fallback, firewall policy checks and hash-chained audit verification.
- Serve or probe MCP: run a stdio MCP server exposing builtin tools, or run a read-only…
- When to use it
- Useful when you want agent workflows defined as local files that can pause for human approval, resume after failure, and be replayed as regression tests, or when you want a small set of builtin file and calculation tools exposed to an assistant over stdio. It is a local, one-shot runner rather than an always-on service.
- Requirements
- A local Python install (3.11 to 3.14) on Linux, macOS or Windows; the package is installed with pip or uvx. Workflows that call models need your own provider keys, pasted into a local .env file, plus optional extras such as openai, anthropic or mcp. Core workflows using only builtin tools need no keys or extras.
Installation
In SourceWeft
- Open ReadyAgents in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ReadyAgents Core
ReadyAgents runs YAML agent workflows locally. Every node is checkpointed, so a run pauses for human approval, resumes from where it stopped, and replays offline as a regression test. Your keys, your machine, no daemon.
Site: readyagents.dev. Repo: github.com/readyagentsdev/readyagents-core.
Tried it? Open an I-ran-this issue. We are not launching. We are listening.
This repository is the free core. You keep the provider account and the bill. Install with pip install readyagentsdev, or from this clone.
60-second start
Requires Python 3.11–3.14 on Linux, macOS, or Windows. Current version is 2.0.12. Install with pip install readyagentsdev, or from this clone. The 2 versions the core contract only; extras carry their own maturity tiers.
The wheel ships the example workflows too — no clone needed:
readyagents new --list-examples shows all of them.
Or from a clone:
readyagents run examples/calc_pipeline.json is the same graph.
HITL next: docs/first-ten-minutes.md.
What it does
- Define agent workflows as YAML or JSON (nodes + edges)
- Run agent, tool, condition, transform, approval, parallel, include, foreach, and decide nodes. Agent nodes may declare a
tools:allowlist for a bounded tool-use loop.type: decideis experimental; see docs/decisions.md. - Persist after every node and resume a paused or failed run from the last successful node
- Inspect past runs:
readyagents runs list/show/replay/fork/diff/freeze/report(local HTML) - Scaffold a starter:
readyagents new my-flow(basic,approval,research,pipeline,review,foreach,agent-tools,gated,decide) - Builtin tools with zero extra servers:
now,calc,json_get,list_dir,read_file,write_file - MCP client and server (
readyagents mcp serve,readyagents mcp probe) with official tasks and MRTR approvals - Policy, spend ledger, budgets and caps: per-node token/cost,
--estimate/--max-spendcaps, model fallback, JSON logs
Beyond the core, 40+ opt-in extras ship in the same install — teams, studio, browser, knowledge, distillation, registry, environments and more. Each is listed with its maturity tier and its limits in docs/extras.md. None of them is required, and none of them changes how the core behaves.
The agent firewall (taint, tool policy, MCP pinning — security model, policy) is defence in depth, not a solution to prompt injection.
Architecture
CLI
Examples (no keys unless noted)
Docs
- Why ReadyAgents?
- Getting started
- First ten minutes
- Concepts
- Configuration (BYOK)
- Workflows
- Authoring (JSON Schema, editors, located errors)
- Connectors (small catalog; write-shaped ops gate by default)
- Sovereign mode (in-process egress refuse, not an OS sandbox)
- Cost / TokenOps (informational vs the provider invoice)
- Time machine (record / replay / fork / diff / freeze)
- MCP · MCP paste catalog
- A2A (untrusted remote content; delegation can exfiltrate; not certification)
- Memory (untrusted; delayed injection and scope escape)
- Scale and batch (opt-in foreground batch; benchmarks labelled engine vs live)
- Streaming (opt-in
--stream; not audio) - Guardrails / output contracts (opt-in
contract:; declared rules) - Multi-agent teams (opt-in
type: team; closed members; no quality claim) - Model routing (opt-in
routing:; declared policy) - Multimodal I/O (opt-in
MediaPart/type: document/type: transcribe; extras; not an OCR claim) - Knowledge pipelines (opt-in
type: ingest; citations/freshness) - Data pipelines (opt-in
type: table/type: classify) - Long-horizon waits (opt-in
type: wait; lazywake) - Event triggers (opt-in
triggers:; no listener in core; at-least-once plus idempotency) - Agent Skills (opt-in
type: skill; open format) - Governed browser use (opt-in
type: browser; declared actions; no CAPTCHA; optional pack) - Conversational sessions (opt-in
type: converse; loopbackserve chat; no audio in core) - Environments and rollout (opt-in
readyagents.env.yaml; pinned releases; gated promote) - Migration (opt-in
readyagents import; structural translation only) - Agent registry (opt-in
readyagents registry; declared roots; draft Annex VIII export) - Distillation (opt-in
readyagents distill; pack-owned training; holdout-gated adapters) - Packaging (opt-in
readyagents package; review-before-install) - Simulation (opt-in
readyagents simulate; declaration-driven cases) - Self-healing (opt-in
readyagents health/recovery:; fingerprints and fail-safe gates) - Benchmarks (opt-in
readyagents bench; offline cassettes) - Packs
- Supply-chain trust (signatures prove origin, not safety)
- Continuous pack (optional, separate distribution)
- Platform support
- CLI
- Compliance evidence (Articles 12–14 mapping; not certification)
- Observability
- Changelog
- Release notes 2.0.12
Install extras
LLM and MCP extras are optional.
From a clone, the same extras are pip install -e ".[openai]" (and anthropic /
gemini / bedrock / vertex / mcp / all). The optional [otel] extra is
not included in [all]; it starts no collector (see
observability.md). The optional [sign] extra (Ed25519
artifact signatures), [jwt], [gemini], [bedrock], [vertex], [image],
[pdf], [audio], and [table] extras are also not in [all]. Unsigned default runs
never import them. Codecs are extras; core installs stay text-only. Pandas is
optional for table ops; stdlib is sufficient.
Then cp .env.example .env and paste your own keys. Core workflows that only use builtin tools do not need extras, keys, or Node.js.
What is not in this repository
Always-on packs are waitlisted and not for sale.
Always-on / continuous workers are not in Core. The optional readyagents-pack-continuous distribution (separate repository, not a Core extra) can run configured workflows from an explicit foreground command. Installing Core still starts no scheduler or listener.
Hosted control plane. Hosted recovery and remote run stores. SSO, multi-tenant teams, billing.
The core has persist, resume, and approval pauses for a local one-shot. It does not run always-on.
License
Apache License 2.0. See LICENSE.
Security
Please report vulnerabilities as described in SECURITY.md. Public contact: [email protected]. Do not commit API keys. Local operator files such as .env are gitignored.
Source: README.md at commit da3a5f0
Tools
0Version history
9- v2.0.12LatestOct 1, 2026
- v2.0.11Sep 30, 2026
- v2.0.10Sep 22, 2026
- v2.0.9Sep 21, 2026
- v2.0.8Sep 20, 2026
- v2.0.6Sep 19, 2026
- v2.0.5Sep 18, 2026
- v2.0.4Sep 17, 2026
- v2.0.3Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts