Skip to content

Releases: readyagents/readyagents-core

ReadyAgents Core 0.8.2

Choose a tag to compare

@readyagents readyagents released this 03 Sep 16:01
74e4ca5

MCP Registry metadata is now included for the local stdio MCP server. The PyPI package README carries the ownership marker.

ReadyAgents Core 0.8.1

Choose a tag to compare

@readyagents readyagents released this 03 Sep 09:57
d468cdb

readyagents is on PyPI. Install docs now match that.

pip install readyagents
readyagents new my-flow

The wheel does not ship examples/. Clone-and-run still uses examples/calc_pipeline.yaml.

Live: https://pypi.org/project/readyagents/0.8.1/

ReadyAgents Core 0.8.0

Choose a tag to compare

@readyagents readyagents released this 02 Sep 11:09
1c481e2

ReadyAgents Core 0.8.0

0.8.0. This package is not on PyPI. Install from a clone (pip install -e .).

First-run clip: https://www.youtube.com/watch?v=D69o_HTGNQk

Eval CLI, local packs, workspace list_dir, extra new templates, unified --json. Still local. No always-on.

What is new

  • readyagents eval scores fixture suites without a network or API keys
  • --pack loads a workspace pack without an entry point
  • list_dir lists a workspace without an MCP filesystem server
  • readyagents new --template foreach|agent-tools|gated
  • --json includes ok and command on operator-facing commands

Try it (no API keys)

Requires Python 3.11+.

git clone https://github.com/readyagents/readyagents-core.git
cd readyagents-core
python -m venv .venv
source .venv/bin/activate   # Windows: .venv\Scripts\activate
pip install -e .
readyagents run examples/calc_pipeline.yaml

Safety

Core still has no always-on listener, scheduler, hosted control plane, extra database, or billing. Packs are not for sale.

Full notes: see CHANGELOG.md (## 0.8.0) and RELEASE_NOTES.md.

ReadyAgents Core 0.7.0

Choose a tag to compare

@readyagents readyagents released this 27 Aug 09:05

ReadyAgents Core 0.7.0

Honest composition resume and a real MCP client. Still local. No always-on. Install from this repo (not claiming PyPI publish).

What is new

  • Include / parallel resume snapshots: successful child nodes and sibling branches are not re-run
  • MCP client: one stdio session per named server; inputSchema on tools; cwd confined to the workspace
  • Pause notify (on_pause_url) uses the same public-IP pin as http_get; HITL still pauses if notify fails
  • Template filters default / len / join and condition and / or / not (no Python eval)

Try it (no API keys)

pip install -e .
readyagents run examples/foreach_calc.yaml
readyagents run examples/composed_gate.yaml --approve gate

Safety

Core still has no always-on listener, scheduler, hosted control plane, extra database, or billing.

Full notes: see CHANGELOG.md (## 0.7.0) and RELEASE_NOTES.md.

ReadyAgents Core 0.6.0

Choose a tag to compare

@readyagents readyagents released this 27 Aug 07:36

ReadyAgents Core 0.6.0

List-shaped local YAML, inspectable tool-use, operable run store. No always-on. Install from this repo (not claiming PyPI publish).

What is new

  • Bounded sequential foreach (items, max_items, resume skips ok items). Example: examples/foreach_calc.yaml
  • json_set / json_merge builtins (size-capped). Example: examples/json_mutate.yaml
  • Agent tools: allowlist + max_tool_rounds; ToolError is a tool observation; tool_rounds on the run record. Example: examples/agent_tools.yaml --dry-run
  • Pause prompt persisted; runs delete / runs gc (paused kept unless --include-paused); Ctrl-C → cancelled; pending cleared on resume/success

Try it (no API keys)

pip install -e .
readyagents run examples/foreach_calc.yaml
readyagents run examples/json_mutate.yaml
readyagents run examples/agent_tools.yaml --dry-run
readyagents run examples/approval_gate.yaml

Safety

Core still has no always-on listener, scheduler, hosted control plane, extra database, or billing. Those remain pack material.

Full notes: see CHANGELOG.md (## 0.6.0) and RELEASE_NOTES.md.

ReadyAgents Core 0.4.0

Choose a tag to compare

@readyagents readyagents released this 25 Aug 22:03
936cbfb

ReadyAgents Core 0.4.0

Docs honesty after 0.3.0. No new nodes. No always-on. Install from this repo (not claiming PyPI publish).

What this labels

  • CHANGELOG Unreleased no longer lists items already in 0.3.0 (#24)
  • first-ten-minutes matches README: readyagents new my-flow (default is pipeline) (#25)
  • Leftover marks extras, size caps, DNS rebind, parallel timeout/retry, packs JSON, and Makefile/CONTRIBUTING smoke as shipped (#26)

The engine is still 0.3.0's.

Safety

Core still has no always-on listener, scheduler, hosted control plane, extra database, or vendor secrets SDK. Those remain waitlisted packs, not for sale.

Full notes: see CHANGELOG.md (## 0.4.0).

ReadyAgents Core 0.3.0

Choose a tag to compare

@readyagents readyagents released this 22 Aug 18:21

ReadyAgents Core 0.3.0

Open-core agent workflow engine + MCP toolkit. BYOK. Install from this repo (not claiming PyPI publish).

Highlights

  • Structured JSON logs, per-node token/cost + budgets
  • Model fallback + circuit breaker; opt-in LLM cache
  • External decision injection: readyagents decide / --decision-file (no always-on HTTP listener)
  • Secrets-manager hooks (env remains default BYOK), audit trail, RBAC + optional PII redaction
  • Pydantic output_schema on agent nodes
  • readyagents.testing helpers; Dockerfile + compose; multi-gate / connector / signed Gate example packs

Safety

Core still has no always-on listener, scheduler, hosted control plane, extra database, or vendor secrets SDK. Those remain waitlisted packs, not for sale.

Full notes: see CHANGELOG.md (## 0.3.0).

ReadyAgents Core 0.2.0

Choose a tag to compare

@readyagents readyagents released this 19 Aug 12:15

ReadyAgents Core 0.2.0

The first release that feels like a toolkit you can trust for one-shot work.

ReadyAgents Core is still the free, open-source engine: YAML workflows, BYOK, builtin tools, MCP optional, packs later. 0.1.0 proved clone-and-run. 0.2.0 is the reliability and operator-experience layer.

Apache-2.0. No vendor keys. No always-on runtime in core.

Why this release matters

A careful engineer running agent graphs needs four things a playground does not:

  1. A human can stop a run. Approval nodes pause (they do not hang a TTY).
  2. A failed step is not a lost run. State is written after every node; resume continues from the last success.
  3. You can see what happened. runs list / show / inspect / replay.
  4. Starting a project is boring in the good way. readyagents new writes a workflow, README, and .env.example.

That is the difference between a demo engine and something you would actually use.

What is new

Human-in-the-loop

- id: gate
  type: approval
  prompt: "Release payment of {{total}}?"
  then: receipt
  else: denied

Without a decision the CLI exits 2, persists paused, and tells you how to continue:

readyagents run examples/approval_gate.yaml
readyagents resume <run_id> --approve gate
# or
readyagents run examples/approval_gate.yaml --approve gate

Durable local runs

JSON under .readyagents/runs/<id>.json, written atomically after each node.

readyagents runs list
readyagents runs show <run_id>
readyagents runs show <run_id> --json
readyagents runs replay <run_id>
readyagents resume <run_id> --approve gate

Filters: --status, --workflow, --limit. Logs include run= and node=.

Composition

  • type: parallel — independent branches concurrently (examples/fanout_gate.yaml)
  • type: include — run another workflow file (examples/include_demo.yaml)

Scaffolding

readyagents new my-flow                     # approval template (default)
readyagents new my-flow --template basic
readyagents new my-flow --template research # parallel + approval

Each writes workflow.yaml, README.md, and .env.example.

Dry-run

Agent nodes report usage: estimated_tokens=…. LLM examples that parse_json after an agent no longer crash on the dry-run stub.

Try it (no API keys)

pip install -e .
readyagents run examples/calc_pipeline.yaml
readyagents runs list

readyagents run examples/approval_gate.yaml --approve gate
readyagents run examples/fanout_gate.yaml --approve gate
readyagents run examples/include_demo.yaml

readyagents new demo --template research
readyagents run demo/workflow.yaml --approve publish

With keys, the existing research / triage / review examples still work. --dry-run still walks them without calling a vendor.

What we deliberately left out of core

These belong in waitlisted packs, not for sale:

  • Always-on / continuous workers and schedulers
  • Hosted control plane, teams, SSO
  • Distributed recovery and remote run stores
  • Alerting, paging, billing

Core stays small so those can plug in via readyagents.packs.

Compatibility

  • Python 3.11+
  • Existing 0.1.0 workflow YAML still runs. New node types (approval, parallel, include) are additive.
  • CLI exit code 2 now means “paused for approval”, not a generic failure.

Docs