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 分