# mini-swe-agent vs Traycer (slim)

> mini-swe-agent scores 59 (C) to Traycer's 57 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mini-swe-agent-vs-traycer.md (~5,300 tokens) · this version ~1,630 tokens · JSON https://www.anchorterminal.com/compare/mini-swe-agent-vs-traycer.json · canonical https://www.anchorterminal.com/compare/mini-swe-agent-vs-traycer
- 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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

mini-swe-agent scores 59 (C) on agent readiness against Traycer's 57 (C), and leads in 3 of 7 scored categories. Traycer leads on schema & documentation and maintenance & community. Both do agent harnesses.

- mini-swe-agent: C 59, rank #715 of 1486 · https://www.anchorterminal.com/tools/mini-swe-agent.min.md
- Traycer: C 57, rank #811 of 1486 · https://www.anchorterminal.com/tools/traycer.min.md
- mini-swe-agent, good for Benchmark runs, research baselines and RL or fine-tuning pipelines that want a minimal, readable agent with a linear trajectory, and for people who want to read every line of their harness. Ahead on Security & auth, 58 against 42; Payments & pricing, 60 against 30. Also Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Ahead on Schema & documentation, 65 against 58; Maintenance & community, 75 against 32.

| Category | mini-swe-agent | Traycer |
| --- | --- | --- |
| Reliability (16%) | 65 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 58 | 65 |
| Agent ergonomics (13%) | 69 | 65 |
| Security & auth (14%) | 58 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 32 | 75 |
| Transparency & trust (7%) | 56 | 60 |

| Fact (where they differ) | mini-swe-agent | Traycer |
| --- | --- | --- |
| Vendor | SWE-bench team (Princeton and Stanford) | Traycer AI |
| Last release | 2026-07-23 | 2026-11-06 |
| Popularity | 8.6k stars, 4.4M PyPI/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Maintenance & community, Traycer +43: mini-swe-agent 32 (2.4.6 on PyPI on 2026-07-23, 104 days before this check, and still the newest tag (10). No release in the 90 days to 4 November (0). Main hasn't moved since 3 September (three commits since 23 July, one from pre-commit-ci). Outside fixes were merged within days through July, but no pull request has been merged since #917 (17 August), 77 of the 85 pull requests numbered after it still carry open merge refs on the git remote, and maintainer reply times couldn't be read; the 18 October shields.io counts are struck (5). The Python library ships in the same package as the CLI and is current (10). Dependabot and pre-commit-ci run, and CI workflows exist with their current state unconfirmed (7).); Traycer 75 (Commits on 6 November 2026 and host 1.5.3 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Payments & pricing, mini-swe-agent +30: mini-swe-agent 60 (Self-hosted rule. No payment protocol (0). Free under MIT with nothing to buy (20). No card or account for the software, and it runs against a local model (20). An agent can install it from PyPI and run a task with no sign-up, given a model endpoint (20).); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Security & auth, mini-swe-agent +16: mini-swe-agent 58 (Harness reading of the framework checklist, used for every harness in this batch. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No telemetry in mini's own source, and prompts go only to the configured provider. LiteLLM's own network behaviour wasn't checked (28). The CLI asks before each command by default, with regex whitelists and `-y` to skip, but the Python `DefaultAgent` never asks, the default local environment has no isolation and passes the full host environment to every command, and the experimental bubblewrap sandbox leaks host variables and shares the network (CVE-2026-108592). Docker forwards no host variables unless listed (8). No prompt-injection guidance found (2). A full trajectory of every command and output saved as JSON after each step, and a trajectory inspector (13). A security policy (docs/SECURITY.md) naming four maintainers to contact by email, with no response time, which meets the disclosure-policy reading at 7 as for cowagent and tokenrip. No bounty or advisory page, and CVE-2026-108592 (VulnCheck, 10 October) still has no fix in any release or on main. Compromised LiteLLM 1.82.7 and 1.82.8 are excluded in the dependency pins since 24 March 2026 (#794) (7).); Traycer 42 (Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.)
- Schema & documentation, Traycer +7: mini-swe-agent 58 (Framework reading. Typed pydantic config classes, typed protocols for agents, models and environments, `py.typed`, a mkdocstrings API reference and a documented trajectory format, but no machine-readable spec for configs or output (15). No llms.txt (/latest/llms.txt and /llms.txt returned 404). The docs are Markdown in the repository, readable raw, though they rely on build-time includes (3). The FAQ and environments page say when to pick mini over SWE-agent and which environment isolates, but the FAQ still says it doesn't use tool calls while the v2 guide says tool calls are now the default (12). Modes are a typed Literal and limits are typed fields, while `model_kwargs` passes free-form to LiteLLM (10). Hello-world and cookbook examples, a model troubleshooting page and a partial list of exit statuses (11). A dated v2 migration guide and kept v1 docs, with release notes only on GitHub, which we couldn't read (7).); Traycer 65 (Harness reading. Mintlify docs, a protocol package and a CLI (65).)