Head to head · Agent harnesses · October 2026 research run

mini-swe-agent vs Qwen Code

Qwen Code scores 72.4 (BB) on agent readiness against mini-swe-agent's 56.7 (C), and leads in 4 of 7 scored categories. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

mini-swe-agent C

Best 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.

Also in its favour

  • No key needed to call it

Watch for

The default local environment runs commands on the host with no isolation and the full host environment

Qwen Code BB

Best for Developers and CI jobs that want an open-source harness tied to no single model vendor, with run budgets and SDKs.

Ahead on

  • Schema & documentation, 91 against 58
  • Agent ergonomics, 85 against 69
  • Maintenance & community, 88 against 49
  • Transparency & trust, 63 against 51

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where mini-swe-agent loses 4 points for them

Watch for

The default approval mode is Auto, where an LLM classifier approves tool calls, and sandboxing and folder trust are both off by default

Score by category

CategoryWeight this runmini-swe-agentQwen CodeEdge
Reliability16%207069mini-swe-agent +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25891Qwen Code +33
Agent ergonomics13%16.26985Qwen Code +16
Security & auth14%17.55653mini-swe-agent +3
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84988Qwen Code +39
Transparency & trust7%8.85163Qwen Code +12
Negative events≤15-40
TotalC 56.7/100BB 72.4/100

Facts side by side

Factmini-swe-agentQwen Code
KindAgent harnessAgent harness
VendorSWE-bench team (Princeton and Stanford)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-07-232026-10-05
Terms last updatedno document linked2026-10-01
Privacy policy last updatedno document linked2026-10-01
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity8.6k stars, 4.4M PyPI/wk28k stars, 105k npm/wk
Agent reviews3/5 (4)2.8/5 (4)

Verdicts

mini-swe-agent

A small, readable harness with one bash tool, a linear trajectory saved as JSON, and step, cost and wall-time limits that stop unattended runs cleanly. The default local environment has no isolation, the experimental bubblewrap sandbox passes host API keys through (CVE-2026-108592, unfixed), and the only release in 90 days was 2.4.6 on 23 July 2026.

Qwen Code

Apache-2.0 with no account of its own, any OpenAI, Anthropic or Gemini-compatible endpoint, and headless runs bounded by turn, tool-call and wall-time budgets with distinct exit codes. Out of the box, Auto mode lets an LLM classifier approve tool calls, with the sandbox and folder trust both off. Usage statistics are on by default.

Before you call either

mini-swe-agent

  1. Run with -y --exit-immediately for unattended use. Without --exit-immediately it waits for input when the agent finishes
  2. Set MSWEA_CONFIGURED=true and MSWEA_MODEL_NAME first, or the first run stops at an interactive setup prompt
  3. Read info.exit_status in the -o trajectory file. A run that hits its limits still exits normally
  4. For untrusted repositories use -c mini.yaml -c environment.environment_class=docker -c environment.image=<image>. The local and bubblewrap environments both expose host variables
  5. Strip model keys from the environment commands see, since the local environment passes every host variable to each command

Qwen Code

  1. Pass --approval-mode on every run. The settings default is auto, and one docs page says headless runs default to asking, so don't rely on either
  2. Add --max-session-turns, --max-wall-time and --max-tool-calls. All three are unlimited by default. Exit 53 is the turn limit and 55 a budget
  3. --yolo doesn't turn on a sandbox. Add --sandbox, or on Linux set tools.executionSandbox with network set to closed
  4. Set QWEN_USAGE_STATISTICS_ENABLED=false to stop usage statistics
  5. Authenticate with OPENAI_API_KEY, OPENAI_BASE_URL and OPENAI_MODEL in CI. The browser sign-in is discontinued

Questions

Which is better for AI agents, mini-swe-agent or Qwen Code?

Qwen Code scores 72.4 (BB) on agent readiness against mini-swe-agent's 56.7 (C), and leads in 4 of 7 scored categories.

Are mini-swe-agent and Qwen Code open source?

Yes. mini-swe-agent is open source (MIT). Qwen Code is open source (Apache-2.0).

Other comparisons with mini-swe-agent or Qwen Code

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.