ReadyAgents

io.github.readyagentsdev由 GitHub 账号 readyagentsdev 发布v2.0.12更新于 Oct 24, 2026

Local YAML/JSON agent workflow CLI with approvals, resume, and optional stdio or loopback MCP HTTP.

概览

AI 生成的概览

本地 CLI,用于运行 YAML/JSON 智能体工作流,支持检查点、人工审批与断点续跑,并可将内置工具以 stdio MCP 服务器形式提供。

可以做什么
  • 编写并运行工作流:用 YAML/JSON 定义节点与连线的图,支持 agent、tool、condition、transform、approval、parallel、foreach、decide 等节点,并可从模板或自带示例生成起始项目。
  • 运行与续跑:每个节点后持久化状态,可暂停等待人工审批,续跑或重放运行,并查看、分叉、对比、冻结历史运行。
  • 使用内置工具:now、calc、json_get、list_dir、read_file、write_file,无需额外服务器。
  • 成本与策略治理:本地花费账本、按节点统计 token 与成本、预估与花费上限、模型回退、防火墙策略检查与哈希链审计校验。
  • 提供或探测 MCP:以 stdio 方式提供内置工具的 MCP 服务器,或对远端端点做只读发现探测。
适用场景
适合希望把智能体工作流写成本地文件、能暂停等待人工审批、失败后可续跑并可作为回归测试重放的场景,也适合把少量内置文件与计算工具通过 stdio 提供给助手。它是本地一次性运行器,而非常驻服务。
运行要求
需要本地 Python 3.11 至 3.14 环境(Linux、macOS 或 Windows),通过 pip 或 uvx 安装。调用模型的工作流需自备服务商密钥,写入本地 .env 文件,并按需安装 openai、anthropic、mcp 等可选扩展。仅使用内置工具的核心工作流无需密钥或扩展。
安装前请注意
工作流可读写本地文件并调用模型服务商,运行前应确认每个工作流及其工具白名单的行为。模型费用计入你自己的服务商账户,花费上限仅供参考,以服务商账单为准。官方称智能体防火墙为纵深防御,并非提示注入的解决方案。不要提交 API 密钥,本地 .env 文件应排除在版本控制之外。

安装

在 SourceWeft 中

  1. 打开 控制台中的 ReadyAgents,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

bash
pip install readyagentsdevreadyagents new my-flowreadyagents run my-flow/workflow.yamlreadyagents runs list

The wheel ships the example workflows too — no clone needed:

bash
readyagents new f --from-example calc_pipelinereadyagents run f/workflow.yaml

readyagents new --list-examples shows all of them.

Or from a clone:

bash
git clone https://github.com/readyagentsdev/readyagents-core.gitcd readyagents-corepython -m venv .venvsource .venv/bin/activate   # Windows: .venv\Scripts\activatepip install -e .readyagents run examples/calc_pipeline.yamlreadyagents runs listreadyagents doctor

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: decide is 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-spend caps, 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

mermaid
flowchart LR  YAML[Workflow YAML/JSON] --> Engine  subgraph Core["ReadyAgents Core"]    Engine[Workflow engine]    Tools[Builtin tools]    LLM[BYOK LLM providers]    MCP[MCP client / server]    Packs[Pack loader]  end  Engine --> Tools  Engine --> LLM  Engine --> MCP  Packs --> Engine  Packs --> Tools  LLM --> OpenAI[OpenAI]  LLM --> Anthropic[Anthropic]  LLM --> Compat[OpenAI-compatible]

CLI

CommandPurpose
readyagents initWrite .env from .env.example if missing
readyagents new [name] [--template basic|approval|research|pipeline|review|foreach|agent-tools|gated|decide] [--from-example NAME] [--list-examples]Scaffold workflow + README + .env.example + local JSON Schema, or copy a shipped example
readyagents import SOURCE PATH [--out DIR] [--explain SOURCE]Import n8n / LangGraph / CrewAI / trigger-action exports (structural translation only)
readyagents validate PATHSchema-validate a workflow (source-located errors on failure)
readyagents schemaPrint/write/check the generated workflow JSON Schema
readyagents eval PATHScore a keyless fixture suite (exit 0/1)
readyagents simulate PATH [...]Declaration-driven cases scored with eval; distinct failures frozen
readyagents optimize PATH --eval SUITEReflective prompt optimization against your eval suite
readyagents prompts list / show / history / diff / rollbackVersioned prompts beside the workflow; rollback restores exactly
readyagents env status / history / diff / deployDeclared environments and pinned releases
readyagents registry scan / annotate / check / list / show / stats / card / exportLocal agent inventory from declared roots (Annex VIII export is a draft)
readyagents distill plan / dataset / train / evaluate / promoteLocal one-node adapters from consented runs (pack trains; holdout required)
readyagents promote PATH --from SRC --to DSTCopy a source pin onto a target after eval/fixture/bench/health/approval gates
readyagents rollback --env NAMERestore the previous release atomically; never auto-forwards
readyagents feedback export / statsConsent-gated correction datasets (production data)
readyagents run PATH [--input KEY=VALUE] [--dry-run] [--approve NODE] [--reject NODE] [--decision-file FILE] [--actor NAME] [--pack PATH] [--policy PATH] [--estimate] [--max-spend USD] [--max-tokens N] [--label KEY=VALUE] [--sovereign] [--stream] [--env NAME]Execute (or --estimate without running). --env runs a pinned release. --stream is opt-in
readyagents batch PATH --input-file FILE [--concurrency N] [--max-spend USD] [--out FILE]Foreground: one workflow, many JSONL/CSV rows (opt-in)
readyagents attest RUN_IDData-residency attestation (technical evidence, not legal compliance)
readyagents bundle --out DIROffline wheel set for pip install --no-index --find-links
readyagents resume RUN_ID [--approve NODE] [--reject NODE] [--decision-file FILE] [--policy PATH]Resume a paused or failed run
readyagents wakeEvaluate wait conditions (lazy; starts no timer or daemon)
readyagents eventInject a signed event (unsigned events are refused)
readyagents policy check PATHValidate a firewall policy file (fail closed)
readyagents policy explain PATH [--policy PATH]Show which tools each node may call and why
readyagents evidence RUN_ID [--out DIR]Local evidence pack
readyagents audit verify [--file PATH]Walk the hash-chained audit trail
readyagents spend [--since DATE] [--by day|workflow|model|actor|label]TokenOps: aggregate the local spend ledger (informational vs the provider invoice)
readyagents graph PATHDeterministic Mermaid routing (executes nothing)
readyagents decide RUN_ID [--file FILE | --node ID --decision approve] [--token-file JWT] [--actor NAME] [--reason TEXT]Inject an approval; --actor stays the default, --token-file identifies
readyagents approvals list [--role ROLE] [--actor NAME] [--expiring-within 1h]Queue of paused gates the caller may see
readyagents delegate --from A --to B --until TS [--scope ROLE]Time-bounded, single-hop, revocable approval delegation
readyagents delegations list | revoke IDList or revoke local delegations
readyagents identity verify --token-file JWTVerify an assertion against local trust anchors
readyagents identity whoamiWorkload fingerprint (never the private key)
readyagents runs listList persisted runs
readyagents runs show RUN_IDNode timeline + stored state (inspect is an alias)
readyagents runs report RUN_IDLocal HTML summary of a run
readyagents runs replay RUN_IDNew run from stored inputs
readyagents runs delete RUN_ID --yesDelete one local run record
readyagents runs gc --yesPrune succeeded/failed/cancelled runs (paused kept; in-window records refused unless --override-retention)
readyagents runs fork / diff / freeze / migrateTime machine: fork a run, diff two, freeze a cassette, migrate JSON→SQLite
readyagents connectors list / show / testSmall governed catalog (rest, sql, object_storage, message, ingest) — not 500 SaaS
readyagents sign / verify / lock / sbom / trustSupply-chain: signatures prove origin, not safety
readyagents approvals serveForeground localhost approval page
readyagents studio [--port 8790] [--open] [--read-only]Foreground localhost canvas and run inspector
readyagents models list / show / route --explainDry model catalog and routing explain (no provider call)
readyagents mcp serveStdio MCP server (builtin tools); --json prints protocol versions
readyagents mcp probe URLRead-only server/discover diagnostic (never calls a tool)
readyagents a2a serve PATHForeground A2A door for one workflow (loopback by default)
readyagents a2a card PATHDeterministic Agent Card (no network)
readyagents a2a probe URLRead-only remote card diagnostic (no secret values)
readyagents memory list / show / search / forget / exportLocal scoped memory (offline except optional embeddings)
readyagents knowledge ...Ingest, sync, cite, and forget knowledge documents (foreground only)
readyagents table ...Inspect intermediate tables: head, schema, stats
readyagents triggers ...Inspect declared triggers, dry-run mappings, list events (starts no listener)
readyagents skills ...Install, list, export, and remove Agent Skills (open format; no marketplace)
readyagents agents-mdEmit project context: how to run, validate, and test workflows here
readyagents package ...Build, install, and catalog workflow packages (review-before-install)
readyagents healthCluster failures by fingerprint over the run store (no daemon, no telemetry)
readyagents bench ...Offline-by-default benchmark suite with labelled engine vs live timing
readyagents sessions ...List, show, close, replay, and freeze conversational sessions (turns are runs)
readyagents serve ...Foreground loopback surfaces (stops with the process)
readyagents packs [--pack PATH]List installed / local packs
readyagents doctorRead-only platform / extras / permissions / loopback / run-store / sovereign diagnostic
readyagents versionPrint version

Examples (no keys unless noted)

FileWhat it shows
examples/calc_pipeline.yamlBuiltin tools, transform, condition
examples/calc_pipeline.jsonSame graph as calc_pipeline.yaml
examples/approval_gate.yamlHuman-in-the-loop pause / resume
examples/ollama_local.yamlKeyless loopback OpenAI-compat path (no live model)
examples/quorum_gate.yamlTwo-approver gate (keyless)
examples/expiring_gate.yamlLazy deadline, on_expire: reject (keyless)
examples/multi_gate.yamlTwo sequential approval gates
examples/fanout_gate.yamlParallel branches + approval
examples/include_demo.yamlSub-workflow include (new --from-example)
examples/composed_gate.yamlInclude + parallel + approval (new --from-example)
examples/research_brief.yamlAgent node (needs a key)
examples/support_triage.yamlClassify then branch (needs a key)
examples/code_review.yamlread_file + review (needs a key)
examples/agent_tools.yamlAgent tools: [calc] (needs a key; --dry-run is keyless)
examples/foreach_calc.yamlSequential foreach + calc (no keys)
examples/policy_gated.yamlPolicy gate on tainted write_file (no keys)
examples/readyagents.policy.yamlStarter firewall policy
examples/json_mutate.yamljson_set / json_merge (no keys)
examples/table_pipeline.yamltype: table + type: classify (validate keyless)
examples/list_dir.yamlBuiltin list_dir (no keys, no MCP, no Node)
examples/eval/pass.yamlKeyless readyagents eval fixture suite
examples/a2a_delegate.yamltype: a2a dry-run (no network)
examples/memory_triage.yamltype: memory write then search (keyless)
examples/code_reshape.yamltype: code JSON in/out (keyless, subprocess)
examples/batch_echo.yamlKeyless readyagents batch row echo (batch_rows.jsonl / .csv)
examples/connector_rest.yamlKeyless rest connector against a local fixture
examples/connector_demo.yamlLocal --pack connector (examples/packs/connector_pack.py)
examples/gated_write.yamlApproval then write_file (no keys)
examples/env/echo.yamlKeyless env deploy + run --env (examples/env/readyagents.env.yaml)

Docs

Install extras

LLM and MCP extras are optional.

bash
pip install "readyagentsdev[openai]"pip install "readyagentsdev[anthropic]"pip install "readyagentsdev[gemini]"pip install "readyagentsdev[bedrock]"pip install "readyagentsdev[vertex]"pip install "readyagentsdev[mcp]"pip install "readyagentsdev[all]"pip install "readyagentsdev[image]"pip install "readyagentsdev[pdf]"pip install "readyagentsdev[audio]"pip install "readyagentsdev[table]"

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.

bash
docker compose run --rm readyagents run examples/calc_pipeline.yamlmake smoke

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.

来源:README.md,提交 da3a5f0

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

9
  1. v2.0.12最新Oct 1, 2026
  2. v2.0.11Sep 30, 2026
  3. v2.0.10Sep 22, 2026
  4. v2.0.9Sep 21, 2026
  5. v2.0.8Sep 20, 2026
  6. v2.0.6Sep 19, 2026
  7. v2.0.5Sep 18, 2026
  8. v2.0.4Sep 17, 2026
  9. v2.0.3Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分