Oh My Subagents CLI
OMS runs Codex and Claude subagent teams as a local service with persistent task state, reusable teams and crash recovery
- 180 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Agent teams work autonomously and run code, edit files and execute commands in the workspace, with rights set by the provider's sandbox modes
- Installs a background service that starts at login and keeps state, task history and provider sign-in data on disk
- Every run spends tokens or Codex and Claude subscription limits, and multi-level teams multiply the spend
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/oh-my-subagentsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Agent teams work autonomously and run code, edit files and execute commands in the workspace, with rights set by the provider's sandbox modes
- Installs a background service that starts at login and keeps state, task history and provider sign-in data on disk
- Every run spends tokens or Codex and Claude subscription limits, and multi-level teams multiply the spend
This is third-party code. Review the repository files before installing.
What it does
OMS moves subagent coordination out of chat and into persistent state. A Manager delegates a Wave of assignments, OMS commits the assignments and the parent's wait as one record, supervises the children and continues the parent when every return of the Wave is in. The parent does not poll its children in a loop, and a closed terminal or an interrupted provider session does not erase what has accumulated. A team is described as a responsibility tree: a Workflow names members and their areas but does not set a schedule. At runtime Managers pick the pattern: sequential, parallel, an implement-review-repair loop or a mix. A run pins exactly the Workflow revision it started with, and the Result is only the lead's accepted answer, completed or blocked. After pipx install oh-my-subagents, oms init picks a workspace, configures a Codex or Claude provider and publishes eight Starter teams, from feature delivery and incident investigation to security audit. oms service install sets up a background service, and the visual Console opens at http://127.0.0.1:18125/. A separate Operator can drive the same operations by chat.
Who it is for. Developers and researchers who run long multi-step tasks on Codex or Claude and are tired of reconstructing from chat who did what.
Good fit when
- A feature crosses contracts, implementation and release, and each part needs its own owner with independent verification
- A serious failure needs competing hypotheses, recovery and verification after the fix
- A large migration goes in dependent batches and progress must survive closing the terminal
- You want independent code review by several agents with one final report
- You want to publish one team of roles once and run it on different tasks
Not a fit when
- The task is small: a multi-agent team adds ceremony and one worker would finish faster
- You only want to launch one agent with command confirmation: OMS manages whole teams and a service
- Python 3.12 or newer and a Codex or Claude account are unavailable: OMS will not start without them
- The Console license does not fit: it ships under the Sustainable Use License and limits commercial redistribution
Example request
Run the security-audit-and-hardening Starter on this repository and send me the final Result with links to the report filesLimitations
- It needs Python 3.12 or newer, Linux, macOS 13 or newer or Windows 11 x64, plus an account and sign-in path for Codex or Claude. On Windows the workspace must sit on a local NTFS volume.
- The code is MIT, but the visual Console in the console folder derives from n8n material and ships under the Sustainable Use License: internal and non-commercial use is allowed, and redistribution is limited to free.
- The default database is SQLite. PostgreSQL needs the package with the postgres extra and schema permissions.
- Existing Banksia installs migrate with oms migrate-from-banksia before oms init. The last commit in the repository is dated September 2026.
How to disable. oms service stop stops the service and oms service uninstall removes its definition while keeping configuration and the database. The package goes away with pipx uninstall oh-my-subagents.
FAQ
What is Oh My Subagents?
A local service that runs Codex and Claude subagent teams and keeps work state outside the chat. Assignments, waits and results live in a database, so a closed terminal does not lose them.
How do I install Oh My Subagents?
Run pipx install oh-my-subagents, then oms init and oms service install. The wizard configures the provider and publishes the Starter teams, and the Console opens at http://127.0.0.1:18125/.
How is OMS different from plain Claude Code subagents?
A plain parent polls its children and assembles answers from the chat. In OMS the controller stores assignments, waits and returned results, and the parent continues when the whole Wave has returned.
Which Starter teams ship with it?
Eight: feature delivery, incident investigation, migration, research with a decision brief, competing prototypes, idea to validated demo, an experiment program and a security audit.
What if I already run Banksia?
Run oms migrate-from-banksia before oms init, then oms db upgrade. Migration keeps configuration, the database, provider credentials and task history, while oms init would create a fresh empty database.
Discussion
No questions or reviews yet.
Related
CLI toolsA multi-agent harness that verifies results by artifacts: stop hooks, an independent judge and an event log for Claude Code, Codex, Cursor and more
Orchestrator plugin for OpenCode and Codex CLI: multiple agents, hooks, built-in MCPs, ultrawork mode and hash-anchored edits
Agents, skills and templates for structured AI development in OpenCode, Codex and Claude Code: docs, plans, review, checkpoints
One agent launches others in the background: Claude Code, Codex, Copilot CLI, Grok Build and Pi, with a model chosen per stage.
An OpenCode plugin that runs a team of parallel agents with separate sessions, a shared task board and messaging
A planner for Claude Code, Codex and OpenCode: one goal becomes a task plan and independent tasks run in parallel
README in short
The README starts by comparing ad-hoc subagents with OMS, then explains Waves, returns and accountability. It continues with pipx installation, upgrading from Banksia, the background service, PostgreSQL, a table of eight Starter teams, the path from prompt to Result, documentation links and the terms of two licenses.