# mini-swe-agent vs T3 Code (slim)

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

- Full: https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code.md (~5,750 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code
- 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 T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on 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
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.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 43; Agent ergonomics, 69 against 60; Security & auth, 58 against 35; Transparency & trust, 56 against 51. Also Free to start without a card.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Ahead on Maintenance & community, 75 against 32.

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

| Fact (where they differ) | mini-swe-agent | T3 Code |
| --- | --- | --- |
| Vendor | SWE-bench team (Princeton and Stanford) | T3 Tools Inc. |
| 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, T3 Code +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).); T3 Code 75 (Commits and nightly tags on 6 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 official apps and install script (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Security & auth, mini-swe-agent +23: 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).); T3 Code 35 (Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.)
- Reliability, mini-swe-agent +22: 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).); T3 Code 43 (Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run 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). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.)
- Agent ergonomics, mini-swe-agent +9: mini-swe-agent 69 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. One bash tool and a short system prompt, with output over 10,000 characters cut to its first and last 5,000, but no compaction of a long history (22). Step, cost and wall-time limits, global call and cost limits by environment variable, and a 30-second timeout per command (18). The trajectory JSON records Submitted, LimitsExceeded, TimeExceeded or RepeatedFormatError, but stdout is human-readable only and these aren't process exit codes (12). Model calls retry ten times with exponential backoff, and the trajectory is saved after every step, but there's no resume and no undo (8). Python bindings only. An unattended `mini` run needs `-y`, `--exit-immediately` and `MSWEA_CONFIGURED`, the last found only in the source (9). No MCP client, ACP or server mode.); T3 Code 60 (Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).)
- Transparency & trust, mini-swe-agent +5: 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).); T3 Code 51 (MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.)