Open Source Coding Agents, Compared
Every agent below ships under a licence GitHub could identify, and every one carries the same FARS review, so the numbers are comparable rather than borrowed from each project's own README. The table leads with the review; the sections under it carry each agent's own positioning, including where its documentation says it is not the right fit.
| # | Agent | FARS | Trust | Stars | License | Language | Last commit |
|---|---|---|---|---|---|---|---|
| 1 | AGF Local Coding Session Finder | 96 | 27/25 | 158 | MIT | Rust | 2026-10-01 |
| 2 | Argot Repository Style Analyzer | 93 | 28/25 | 51 | MIT | Rust | 2026-09-02 |
| 3 | Codex Autoresearch | 91 | 27/25 | 834 | Apache-2.0 | TypeScript | 2026-10-02 |
| 4 | jev-axi Judgment CLI | 90 | 23/25 | 43 | MIT | TypeScript | 2026-09-24 |
| 5 | Zoetrope | 89 | 23/25 | 1.1k | MIT | Rust | 2026-09-11 |
| 6 | agnix Config Linter | 89 | 27/25 | 455 | Apache-2.0 | Rust | 2026-10-18 |
| 7 | Mirafold | 89 | 25/25 | 18 | MIT | TypeScript | 2026-09-16 |
| 8 | CommitLore | 89 | 25/25 | 18 | MIT | TypeScript | 2026-10-18 |
| 9 | elizaOS | 88 | 24/25 | 19.6k | MIT | TypeScript | 2026-10-18 |
| 10 | Pi Dynamic Workflows | 88 | 23/25 | 555 | MIT | TypeScript | 2026-10-06 |
| 11 | Piia Engram | 88 | 27/25 | 162 | AGPL-3.0 | Python | 2026-10-10 |
| 12 | YYLO CLI | 88 | 25/25 | 65 | MIT | Python | 2026-10-15 |
The order is the FARS total; stars only break ties, because popularity measures attention rather than whether something holds up. Two limits are worth knowing before you read the order. These are static reviews — source, documentation and repository metadata, with no runtime reproduction — which caps reliability, effectiveness and verifiability and puts the achievable maximum at 77 rather than 100. And a gap of a few points sits inside the noise of that method. Read the table as a shortlist worth investigating, not as a verdict; every score links to its full dimension breakdown and the evidence behind it. Review method →
1. AGF Local Coding Session Finder
Search and resume locally stored AI coding sessions from one terminal interface.
Where it differs
Compared with opening each agent's native session picker or manually searching history files, AGF provides one searchable view across 16 tools plus common JSON and MCP query interfaces. It does not replace those agents, however: each native CLI still performs the resume, and some providers' sessions must be deleted through their own picker to preserve upstream state.
2. Argot Repository Style Analyzer
Learn unwritten conventions from Git history and flag changes that diverge from the repository.
Where it differs
A type checker asks whether code satisfies its type constraints; Argot asks whether a change resembles the code, layout, and dependency direction established by that repository. Unlike sending the code to a second LLM for an opinion, Argot derives findings from local statistical, graph, scripted, and embedding evidence, with no generative or opinion-forming model deciding the result. The tradeoff is that it remains a repository-specific review guardrail, not a general correctness oracle.
3. Codex Autoresearch
Run measurable optimization loops inside your codebase: give it a goal, a benchmark, and a boundary, and it experiments, keeps evidence, and leaves a reviewable patch.
4. jev-axi Judgment CLI
Fast probabilistic safety and workflow judgments for coding agents, shell commands, diffs, logs, and untrusted text.
Where it differs
Unlike foreman, which runs Jev as a supervisor above a coding agent, jev-axi does not launch the agent; it connects similar completion and progress judgments to the agent's existing hooks. It also differs from generative coding models: Jev returns typed probabilistic judgments and never writes prose, so jev-axi complements rather than replaces code generation and code comprehension.
5. Zoetrope
Watch a Claude Code session as a live flow graph — main agent, subagents and tool calls — in your terminal or browser.
6. agnix Config Linter
Find and fix broken AI coding-assistant configurations before they disrupt development workflows.
7. Mirafold
Run and supervise your local coding agents from a browser.
Where it differs
Compared with using Claude Agent, Codex, OpenCode, or Gemini CLI directly in a terminal, Mirafold keeps the native agent and its local permission model while adding a browser UI, structured generative components, multi-session supervision, and adjacent file and Git views. It is not a unified proxy agent and does not replace those CLIs with its own generic implementation. Each supported agent has a separate adapter, so live availability still depends on that backend and its authentication.
8. CommitLore
Give coding agents only the Git-owned decisions, constraints, and warnings that still apply.
Where it differs
General memory or RAG systems primarily ask which old text is semantically related. CommitLore instead asks which recorded decisions still apply to a particular repository path now. Git is the authority, records have active, superseded, or expired lifecycle states, and delivered material is graded as directive, claim, or blocked rather than treating every relevant passage as current guidance. That narrower design means it is not intended to replace conversation archives, general user memory, or vector databases.
9. elizaOS
An open-source TypeScript system for building, running, and extending autonomous AI agents.
Where it differs
Compared with the optional Eliza Cloud path, the local runtime and direct-provider configuration remain first-class options: Eliza Cloud adds accounts, authentication, hosted model routing, application and agent deployment, remote connectivity, and cross-device services, while the other paths preserve more direct runtime and provider control. For whole-device delivery, this monorepo retains Eliza application shells and native runtime bridges, whereas the separate elizaOS/os repository owns bootable Linux and AOSP distributions, installers, release manifests, and OS toolchains.
10. Pi Dynamic Workflows
Turn complex Pi requests into routed, resumable, cross-checked fleets of parallel subagents.
Where it differs
The project explicitly maps itself to Claude Code dynamic workflows: both use code-mode orchestration, isolated subagent contexts, structured outputs, background execution, model selection, and resume. This Pi implementation additionally documents Git worktree isolation, measured cost accounting, an interactive /workflows TUI, deep research, and reusable quality helpers. It is not presented as a Claude Code extension, and the source does not document direct execution inside Claude Code.
11. Piia Engram
A user-owned local identity and long-term knowledge layer shared across AI coding tools.
Where it differs
Compared with Claude Memory, Piia Engram keeps its records in user-controlled local files and targets multiple MCP tools instead of the Claude ecosystem alone. Compared with CLAUDE.md or .cursorrules, it preserves personal preferences, lessons, and decisions across repositories; repository rule files remain the better place for project-specific build steps and conventions. Mem0, Zep, and Letta focus on task or session memory for agents, whereas Piia Engram focuses on the person behind those tasks and their enduring work standards. The official @modelcontextprotocol/server-memory provides a generic entity-relation knowledge graph, while Piia Engram adds structures specifically for developer identity, quality standards, lessons, decisions, and governed review.
12. YYLO CLI
Orchestrate coding agents, repository tasks, validation, and protected merges with durable receipts.