# mini-swe-agent vs Paseo (slim)

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

- Full: https://www.anchorterminal.com/compare/mini-swe-agent-vs-paseo.md (~5,100 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/compare/mini-swe-agent-vs-paseo.json · canonical https://www.anchorterminal.com/compare/mini-swe-agent-vs-paseo
- 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)

Paseo scores 62.1 (B) on agent readiness against mini-swe-agent's 59 (C), and leads in 4 of 7 scored categories. mini-swe-agent leads on reliability. Both do agent harnesses.

- mini-swe-agent: C 59, rank #719 of 1510 · https://www.anchorterminal.com/tools/mini-swe-agent.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.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 Reliability, 65 against 50. Also Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Schema & documentation, 65 against 58; Maintenance & community, 75 against 32; Transparency & trust, 68 against 56.

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

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

Why the edge:
- Maintenance & community, Paseo +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).); Paseo 75 (v0.15.3 and commits on 7 November 2026 (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 builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Reliability, mini-swe-agent +15: mini-swe-agent 65 (Read as a local package, graded on 2.4.6, the release `pip install mini-swe-agent` installs, and still the newest tag on 4 November 2026. One official PyPI package with Python 3.10 or newer stated (20). A pytest workflow runs on every push to main with Podman, bubblewrap and Apptainer installed, 41 test files and Codecov coverage, but GitHub's pages refused this run, so whether main passes is unconfirmed (15). Issue counts and types couldn't be read (the 18 October counts came from shields.io, a third-party copy, and are struck). The git remote shows outside bug fixes merged through 22 July, such as #915, #896 and #886, and nothing merged into main since apart from a pre-commit update on 17 August, while 77 of the 85 pull requests numbered after #917 still carry open merge refs (10). Versions follow semver and v2's breaking changes came with a migration guide, but there's no changelog file and tags carry only a version bump (8). 2.4.6, past 1.0, though the PyPI classifier still says 3 - Alpha (12).); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Transparency & trust, Paseo +12: mini-swe-agent 56 (MIT (30). No privacy policy, terms or data-handling statement, though the tool runs locally and collects nothing we could find (8). A v2 migration guide marks the breaking changes, says how to pin `mini-swe-agent~=1.0`, and keeps v1 docs and a v1 branch, but there's no deprecation policy or end date for v1 (10). No telemetry in the source, but the docs don't say so (14).); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)
- Schema & documentation, Paseo +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).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)