
Minimal open-source coding agent with a CLI, bash-first control loop, and benchmark-grade SWE-bench performance
Do not bounce yet
Read the fit check, compare one alternative, then decide whether the vendor page is still your best next click.

Quick Verdict
Make the fit call first. Vendor pages are good at selling, but they rarely tell you where the product is a bad match.
Compare Next
This is where visitors usually jump out too early. Read one deeper take or open one alternative so the next click is informed instead of impulsive.
Alternative profile
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Alternative profile
Agentic AI coding assistant that lives in your terminal, understands your entire codebase and automates routine tasks
Alternative profile
Beautiful chat interface for Claude Code right inside VS Code, no terminal required
mini-swe-agent matters because it takes the opposite path from most agentic coding launches. Instead of piling on interfaces, tools, and orchestration layers, it asks whether a much smaller bash-first agent can still solve real software tasks. In 2026 that is not just an aesthetic argument: the project is positioned by its own creators as the default choice over full SWE-agent for many users, and it is already being used as both a practical CLI tool and a serious benchmark harness.
mini-swe-agent is one of the more credible 2026 additions in agentic coding because it cuts away a lot of the usual scaffolding instead of adding more theater. Built by the SWE-bench and SWE-agent team, it runs a radically simple bash-first loop that can solve GitHub issues, help inside your command line, and serve as a serious baseline for benchmarking or local automation. If you want a hackable CLI agent with transparent control flow rather than a black-box IDE product, this is a real contender.
mini-swe-agent is unusually clear about what it is optimizing for: simplicity, inspectability, and practical shell-driven execution rather than UI theater.
The official docs explicitly push users toward mini-swe-agent as the default path, which is a stronger product signal than a repo that is merely adjacent to a bigger brand.
It is relevant both for real coding-agent usage and for evaluating model performance on SWE-bench-style tasks, which makes it more durable than a novelty launch.
If you want an open-source CLI agent that is lighter than OpenHands and less workflow-heavy than full SWE-agent, this is one of the sharper options to evaluate.
Terminal-first CLI (`mini`) built around a radically simple bash-only agent loop instead of a giant custom tool scaffold or monorepo-heavy control plane
Strong benchmark positioning with the project currently claiming >74% on SWE-bench verified while staying intentionally lightweight and inspectable
Supports local environments plus multiple sandboxing paths including Docker, Podman, Singularity/Apptainer, Bubblewrap, Contree, and related execution setups
Broad model compatibility through LiteLLM plus support paths such as OpenRouter and Portkey, which keeps it from being trapped behind one vendor stack
Includes batch inference workflows, a trajectory browser, and Python bindings instead of stopping at a single interactive CLI surface
Official docs now recommend mini-swe-agent as the default choice over the heavier full SWE-agent for many practical use cases
Use mini-swe-agent when you want a lightweight agent in your own terminal that can inspect repos, run commands, and work through GitHub-style software tasks without a large hosted control plane.
The project is especially relevant if you care about measuring model performance on SWE-bench-style tasks with a simpler, more transparent agent scaffold.
mini-swe-agent is a good fit for teams that want to understand or extend the agent itself rather than merely consuming a closed product surface.
It makes sense when bash is the real tool you want the model to learn to use well, rather than wrapping every action behind custom interfaces and abstractions.
Developers who want a terminal-native open-source coding agent without a huge framework footprint
Researchers and benchmark-minded teams comparing model behavior on coding-agent tasks
Engineers who prefer inspectable bash-centric control flow over opaque hosted automation layers
Builders comparing mini-swe-agent with SWE-agent, Aider, OpenHands, or Claude Code
Running a lightweight coding agent locally in the terminal to solve GitHub issues, inspect repositories, and execute bash-driven implementation loops
Evaluating frontier or open models on SWE-bench-style workflows without dragging in a huge custom agent framework
Research, fine-tuning, or RL work where a simple and transparent agent scaffold is more useful than a feature-stuffed platform
Teams that want a hackable open-source baseline to compare against Aider, Claude Code, OpenHands, or full SWE-agent
mini-swe-agent review
mini-swe-agent vs SWE-agent
minimal open source coding agent
bash-first coding agent
mini-swe-agent SWE-bench
mini-swe-agent alternatives
Developers compare mini-swe-agent with other vibe coding tools when they need a better workflow fit, not just a better landing page.
SWE-agent
Aider
OpenHands
Claude Code
Open-source terminal session manager for running and supervising multiple AI coding agents across isolated git worktrees.
Open-source terminal and web session manager for running multiple AI coding agents across isolated git worktrees and sandboxes.
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Agentic AI coding assistant that lives in your terminal, understands your entire codebase and automates routine tasks
Beautiful chat interface for Claude Code right inside VS Code, no terminal required
Open-source terminal dashboard for tracking Claude Code token usage, burn rate, and predicted session cutoffs.
Source-available coding agent platform with a web GUI, CLI, and SDK for running autonomous software tasks locally or in the cloud.
Strong picks usually survive one more internal check. Read deeper, compare a neighbor, then leave for the vendor page if the fit still holds.