# agents-tree vs Overmind (slim)

> agents-tree scores 64.3 (B) to Overmind's 58.5 (C) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agents-tree-vs-overmind.md (~4,550 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/agents-tree-vs-overmind.json · canonical https://www.anchorterminal.com/compare/agents-tree-vs-overmind
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

agents-tree scores 64.3 (B) on agent readiness against Overmind's 58.5 (C), and leads in 2 of 7 scored categories. Overmind leads on schema & documentation and maintenance & community. Both do agent tracing.

- agents-tree: B 64.3, rank #401 of 1266 · https://www.anchorterminal.com/tools/agents-tree.min.md
- Overmind: C 58.5, rank #650 of 1266 · https://www.anchorterminal.com/tools/overmind.min.md
- agents-tree, good for Seeing every coding-agent session and its sub-agents as one tree in a terminal Ahead on Reliability, 60 against 23; Payments & pricing, 60 against 30. Also No key needed to call it.
- Overmind, good for A team that wants to go from agent traces to a fine-tuned small open model in one place, driven by a coding agent. Ahead on Schema & documentation, 81 against 64; Maintenance & community, 76 against 63. Also A hosted endpoint, with nothing to install.

| Category | agents-tree | Overmind |
| --- | --- | --- |
| Reliability (16%) | 60 | 23 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 81 |
| Agent ergonomics (13%) | 73 | 76 |
| Security & auth (14%) | 66 | 70 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 63 | 76 |
| Transparency & trust (7%) | 62 | 65 |

| Fact (where they differ) | agents-tree | Overmind |
| --- | --- | --- |
| Kind | Agent framework | HTTP API |
| Vendor | Karel Blavka | Overmind Technology Ltd |
| Hosted endpoint | no (local only) | `https://api.overmindlab.ai` |
| Transports |  | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT (Copyright (c) 2026 Karel Blavka) | AGPL-3.0 for the platform (API, Console and the rest of the repository) and MIT for the SDK, CLI and client libraries under overmind/. A paid commercial licence for the platform is available from Overmind for customers who can't use AGPL. The hosted service is under Overmind's terms of 1 March 2026 |
| Tools exposed | none | 85 |
| llms.txt | no | yes |
| Last release | 2026-10-08 | 2026-10-31 |
| Terms last updated | couldn't be read | 2026-03-01 |
| Privacy policy last updated | no document linked | 2026-10-03 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 732 stars |

Why the edge:
- Reliability, agents-tree +37: agents-tree 60 (Local-package reading, as for agent-tree, superpowers and tokeneconomizer. Installs from PyPI with `uv tool install agents-tree` or pipx, with Python 3.10 or later and POSIX stated in pyproject.toml and Linux and macOS in the herdr manifest (20). .github/workflows/test.yaml runs pylint, pyright, 173 pytest tests, a test run and a package build on Python 3.10 to 3.14 on every push and pull request. Whether the runs pass wasn't checked, as github.com couldn't be read (15 of 25). Issues couldn't be read for the same reason (5 of 25, unchecked). Semver tags and Conventional Commit messages, but no changelog, and the README's caveat that transcript formats may change is the only note on breakage; the switch to reading every provider by default came with 1.0.0 (5 of 15). Version 1.2.0 (15). 60 in all.); Overmind 23 (No status page. status.overmindlab.ai doesn't resolve, /status returns 404 and neither the site nor the docs link one (0). With no history to read, 5. No request rate limits for the REST API, MCP or OTLP ingest were found in the docs. The only pacing settings, `JEV_REQUESTS_PER_MINUTE` and `JEV_TOKENS_PER_SECOND`, are self-hosting configuration for the scoring model (0). No 429 or Retry-After guidance, but the docs give safe-retry rules in detail. Launches, uploads, pipeline runs and inference take a stable `request_key`, identical retries return the existing receipt, changed payloads conflict, and `run_evaluation` is named as not idempotent (8). The terms promise commercially reasonable efforts toward 99.5 per cent availability a month, with remedies only in an order form or separate SLA, so half (5). The site doesn't call the service beta, but the SDK is classed "3 - Alpha" on its package metadata and the public repository is seven weeks old (5). 0+5+0+8+5+5 = 23.)
- Payments & pricing, agents-tree +30: agents-tree 60 (Self-hosted rule. No payment protocol (0). Free under MIT with nothing to buy (20). No card or account (20). A person installs it from PyPI with one command and no sign-up (20). 60 in all.); Overmind 30 (No x402 or other machine payment. Paid work spends prepaid credits, and `402` is documented only for insufficient credits (0). Plan prices, the credit rate ($0.01) and per-model "from" prices for training and serving are published without login (20). A Free plan with $50 of credits once exists, but neither the pricing page nor the docs say whether a card is needed, so half (10). A person signs up in a browser at console.overmindlab.ai. MCP OAuth with dynamic registration still needs a sign-in, and `create_api_key` needs an existing connection (0). Self-hosting under AGPL is free but runs on the operator's own Modal, OpenRouter, AWS and Hugging Face accounts, so it isn't scored as the hosted option. 0+20+10+0 = 30.)
- Schema & documentation, Overmind +17: agents-tree 64 (Framework reading, docs a model can follow, as agent-tree was read. `--json` writes one document with `schema_version` 1 and a fixed set of session, agent and detail fields, and model.py types them as dataclasses, but no JSON Schema or field reference is published (14 of 25). README, AGENTS.md and docs/demo are Markdown in the repository; no llms.txt (10). The README says what it shows and reads, has a caveats section per provider (context window inference, internal formats, how running sessions are found), and the command's help says not to run it inside an agent (15 of 20). argparse with choices for --provider and --color, positive-number checks for --window and --interval, and --json refused with --watch (10 of 15). Usage examples for every flag, key and column tables, and errors as messages on stderr with exit code 1, with few error outputs documented (10 of 15). Semver tags and a schema version, no changelog (5 of 15). 64 in all.); Overmind 81 (The docs say each deployment serves its OpenAPI schema at `/api/schema/`, and the repository holds a generated client of 451 files under frontend/src/openapi. api.overmindlab.ai's robots.txt allows only /.well-known/, so the schema itself wasn't read. Every MCP tool takes a Pydantic input model with `extra="forbid"`, compiled to JSON Schema in overbae/services/mcp/catalog.py, read in the source at main on 31 October 2026 (25). llms.txt with 42 pages, llms-full.txt and Markdown for every page on Mintlify (10). Tool descriptions say what each does and what it doesn't ("Does not activate application routing", "no execution", "Passive: never starts provider work"), and the MCP reference warns that an inspection-style name doesn't mean zero cost. Some workbench descriptions are clipped to the point of being hard to parse (16). Typed inputs with Literal enums, length and range bounds, UUID formats and required fields (13). The docs have worked examples for the CLI, SDK, OTLP and inference, and document status classes (401, 402, 403, 404, 409) and structured MCP errors with code, message, retryability and field details, without a full error-code list (10). The MCP server exposes a contract version and a catalogue fingerprint at `overmind://interface/current`. The SDK changelog has one undated Unreleased section and no product changelog was found (7). 25+10+16+13+10+7 = 81.)
- Maintenance & community, Overmind +13: agents-tree 63 (1.2.0 on PyPI on 8 October 2026, 24 days before the check, and a commit on main on 11 October (30). Five PyPI releases between 7 and 8 October 2026 (20). Issue and pull-request replies couldn't be read, as github.com was unreachable. The bare clone shows two Dependabot branches of 28 October unmerged (5 of 25). Not an MCP server and in no official directory; herdr's plugin marketplace couldn't be read (0). No runtime dependencies, a lock file, CI on five Python versions and Dependabot for the workflow actions, with its two updates unmerged (8 of 10). 63 in all.); Overmind 76 (overmind 0.1.115 on PyPI on 2026-10-31, and the last commit on main the same day (30). 41 PyPI releases since 21 September 2026 and 24 git tags from v0.0.15 on 18 September to v0.1.23 on 30 October (20). github.com answered 403 to this session, so issues and pull request replies weren't read. 172 commits on main from eight people since 15 September, a Discord server and a support email (8). One official SDK, Python, current with the platform (10). Public CI workflows for the platform and SDK, Dependabot bumps merged on 28 October and a CI badge. We couldn't see the pass state (8). 30+20+8+10+8 = 76.)