Coding agent

mini-SWE-agent

Minimal bash-only coding harness for inspectable CLI use and reproducible research.

Status
Active
License
MIT
Evidence
Documented + code-verifiable + independently measured configuration, 23 sources
Product record checked
2026-07-27

At a glance

A deliberately small open-source software-engineering agent with one linear bash-only loop, confirm, yolo, and human control modes, versioned trajectories, local-model routing, optional isolated environments, and batch evaluation runners.

Good choice if

  • Transparent baselines and controlled model-harness studies
  • Developers who want a simple CLI with confirmation before each proposed action
  • Pinned SWE-bench or ProgramBench batches with structured trajectory output

Check before choosing

  • The default local environment executes directly with the user's host privileges; isolation is opt-in
  • Confirm mode prompts per proposed action, but it is not a scoped permission policy and there is no rollback checkpoint
  • The bash-only surface omits MCP, browser tools, delegated agents, and persistent memory
See 2 more considerations
  • Local models require a compatible endpoint and may need manual cost-registry configuration
  • Interrupted batch runs are rerun manually; trajectories are written only after a task completes

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Reusable skills
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution
DocumentedDocumented execution-isolation mechanismSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Getting started

Run mini-SWE-agent 2.4.6 with `uvx mini-swe-agent`, select a model, then deliberately choose the default host environment or an isolated Docker, SWE-ReX, Bubblewrap, or related backend.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationSandbox availableDocumented mechanism, not a performance score.
  • Tooling & integrationsBuilt-in toolsDocumented mechanism, not a performance score.
  • Context & stateBasic sessionDocumented mechanism, not a performance score.
  • Lifecycle & recoveryManual recoveryDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationManualDocumented mechanism, not a performance score.
  • Governance & permissionsApproval promptsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

5/5public artifacts present
Security policy
Present at inspected commit
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Present at inspected commit
Contributor documentation
Present at inspected commit

The v2.4.6 tree contains 42 Python test files and six GitHub Actions workflows. Its SWE-bench and ProgramBench runners, configs, and trajectory utilities are project-owned evaluation assets rather than independent performance evidence; the separately admitted Terminal-Bench 2.1 run is pinned to mini-SWE-agent 2.4.5 and complete Harbor metadata.

Inspect commit a83fcae82d2a08f0ee0c688f9d137b3566c097f8, checked 2026-07-27
Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage
  • Latest stable releasev2.4.6Released 2026-07-23; 6 stable releases in 90 daysOpen release
  • GitHub stars7.18KFull-source repository; 993 forksOpen artifact

Routing, package retrievals, release downloads, editor installs, and repository interest observe different populations. They are never added together and never affect capability evidence, classification, or measured results.

Interpretation rulesSignals checked

First-party evidence

Each capability claim links to the first-party record that supports it.

23 first-party sourcesProduct record checked

Additional first-party sources

23 sources
View 22 more sources