oh-my-openagent vs SWE-agent
oh-my-openagent is much bigger: 68.7k stars against 20.2k. Over the days we have tracked them oh-my-openagent moved +4.2% and SWE-agent +4.1%, so oh-my-openagent is growing faster right now.
oh-my-openagent leads on context depth. SWE-agent does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Orchestrates multiple agent harnesses and parallel "discipline" agents (Team Mode) to run whole-repo autonomous workflows rather than a single-model single-agent approach.
- Stars
- 68.7k
- Tracked growth
- +4.2%
- Maturity
- ●●●●●
- Last commit
- 12m ago
- Language
- TypeScript
- License
- NOASSERTION
- Cost to run
- Requires your provider subscriptions / API keys
State-of-the-art open-source agent focused on autonomously fixing GitHub issues and offering a specialized EnIGMA mode for offensive cybersecurity, all governed by a single YAML.
- Stars
- 20.2k
- Tracked growth
- +4.1%
- Maturity
- ●●●●●
- Last commit
- 4d ago
- Language
- Python
- License
- MIT
- Cost to run
- Your API key (cloud LMs)
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | oh-my-openagent | SWE-agent |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Basic filters | ●●●●● Basic config filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config + plugins | ●●●●● YAML config |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Cloud APIs (your key) | ●●●●● Your API key |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multi-provider / BYOK | ●●●●● Any BYO model |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● One-click demo |
Which one to pick
Pick oh-my-openagent if…
Multi-provider orchestration — choose this when you want an open, extensible agent harness that coordinates many models/agents for complex, whole-repo automation and installs quickly via a one-line command.
- Context depth: Whole-repo analysis (5/5 against 3/5)
Pick SWE-agent if…
SOTA performance — pick SWE-agent when you want a research-grade, configurable autonomous agent (with an easy Codespaces demo) that can fix repo issues and run security experiments.
What people want from each one
code-yeongyu/oh-my-openagent
Hacker News: Agent-Model Matching Guide drew 2 points and 0 comments.
SWE-agent/SWE-agent
Hacker News: Princeton group open sources "SWE-agent", with 12% fix rate for GitHub issues drew 307 points and 143 comments.
Questions people ask
Is oh-my-openagent better than SWE-agent?
oh-my-openagent leads on context depth. SWE-agent does not take any axis by a clear margin. oh-my-openagent is worth picking when multi-provider orchestration — choose this when you want an open, extensible agent harness that coordinates many models/agents for complex, whole-repo automation and installs quickly via a one-line command.
Which of oh-my-openagent and SWE-agent keeps my code private?
oh-my-openagent: Cloud APIs (your key) (3/5). SWE-agent: Your API key (3/5).
What does each one cost to run?
oh-my-openagent: Requires your provider subscriptions / API keys. SWE-agent: Your API key (cloud LMs).
Full profiles: code-yeongyu/oh-my-openagent and SWE-agent/SWE-agent. Everything else in Autonomous SWE agents.