Our take
Newless than six months old and changing fast- Activity
- 65
- Community
- 13
- Issues
- 21
- Pull requests
- 70
- Fewer contributors than 82% of the projects we track
AgentRun is an unusually broad, actively changing agent platform and workflow toolkit, but its newness and dependence on one primary contributor make it a higher-uncertainty choice for production adoption.
Good fit if
- You want to self-host a platform that records agent revisions and runs, and are comfortable operating a beta-stage project.
- Your workflow needs explicit typed decisions, review paths, or agent tasks rather than only a fixed sequence of application functions.
- You use Pi and want its durable runtime and workflow packages as building blocks.
Look elsewhere if
- You need a mature project with demonstrated release history and broad contributor ownership.
- Your agents must use a harness other than Pi, Claude Agent SDK, or Codex, or you need a harness package that is already published rather than held.
- You want typed decisions to guarantee factual correctness. The project explicitly notes that schemas and decision thresholds do not establish truth.
All health signals
| Last commit | 2026-11-02 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 1 (latest gallery, 2026-10-20, pre-release) |
| Contributors | 3 (top contributor: 100% of commits) |
| Issues closed, last 90 days | 0+ |
| Pull requests merged, last 90 days | 28 (typically merged in 0 days) |
| Project age | 40 days |
Checked on 2026-11-02 with the GitHub API.
Overview
AgentRun is a platform for creating and changing agents, then running them with a record of the exact revision used. Its server exposes agent revisions and runs through one API and page. The platform runs on Pi by default, with Claude Agent SDK and Codex available as named harnesses when supported by the server. AgentRun builds on Pi’s durable runtime, including pi-durable and chord.
The accompanying TypeScript workflow DSL describes repeatable steps, typed decisions, and calls to agents. This is aimed at teams that want workflows they can inspect, test, and run through an agent platform rather than keeping the process only in application code. You can self-host the server or use the packages individually in a Pi-based application.
Key Features
- Store agents, revisions, and runs together, with each run tied to the revision it used.
- Host the server in a Docker container, with its data kept in a mounted directory.
- Define workflows as JSON or with a TypeScript builder and Zod contracts.
- Combine tool calls, Jev typed decisions, and agent tasks, with branching, parallel work, and bounded loops.
- Run scripted demos and tests without model keys before connecting live model services.
- Use the Pi extension to build, inspect, and run workflows from Pi.
- Add separate packages for browser access, document and video vision, tool transport, and durable agent storage.
Use Cases
- Support teams can search for an answer, check it against defined criteria, ask an agent to investigate when needed, and route unresolved cases for review.
- Developers integrating agents into an application can put repeatable steps and decision thresholds in a workflow, then connect their existing tools and agent through adapters.
- Teams reviewing agent behavior can inspect which agent revision ran and examine the corresponding run record.
- Pi users can create and execute workflows from the Pi coding agent, including scripted runs that do not require model calls.
What you need
Detected in the repository
- Node.js >=22.19.0 (from package.json)
- A test suite and automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
For a scripted DSL demo with no API key, use Node.js 22.19 or newer:
npm install @parcha/agentrun-dsl@beta
npx @parcha/agentrun-dsl@beta demo
To try the self-hosted platform, see the repository README and AgentRun Server guide.
Alternatives
- swarmclaw: SwarmClaw focuses on coordinating persistent, tool-using agents with schedules and delegation, while AgentRun centers on versioned agents and inspectable workflow runs.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| AgentRun | TypeScript | Apache-2.0 | 423 | New |
| swarmclaw | TypeScript | MIT | 697 | Quiet |
Considerations
- The project is very new and changing quickly. Recent activity is high, but most contributions come from one person; the measured data also shows no issues closed in the recent period, despite merged pull requests.
- Published packages are distributed under the
betatag, and the latest listed release is a prerelease. Several packages and non-Pi harness adapters are held back from npm. - The server and workflow tools still require you to supply model access for live runs. The scripted examples avoid that requirement, but do not demonstrate live model behavior.
- Workflow code nodes run with process privileges. The README warns that hosts must provide a controlled sandbox when workflow authors are untrusted.
- Self-hosting with persistent run history requires durable storage. The README notes that Render's free instance has no disk and loses data when it sleeps or restarts.
Found this useful?
Share it with someone who would like AgentRun.