OMS is a local, visual runtime for persistent Codex and Claude teams. One lead owns the task; managers coordinate major parts; contributors complete focused assignments. Teams work sequentially, in parallel, in batches, or through ralph style loops. OMS records every handoff, recovers after interruptions and errors, and returns one explicit completed or blocked Result. Free and self-hosted, MIT-licensed.
I built Oh My Subagents because starting subagents was easy, but operating them across long, consequential work was not. Parents ended up polling, reconstructing ownership from chat, and trusting provider “done” messages that did not prove the whole task was actually complete.
OMS is a local runtime for persistent, supervised Codex and Claude teams. Every team has one lead who owns the complete task and its final Result. Beneath the lead, managers own major parts of the work, delegate focused assignments, and integrate what their teammates return. Contributors complete those focused assignments and return their findings, changes, or verification.
During a run, the lead and managers choose the pattern that fits the work: sequential steps, parallel investigation, batches divided among contributors, or repeated implement–review–repair cycles—including Ralph-style loops. OMS records every assignment and return, preserves the team’s waiting and recovery state, and resumes the right owner after interruptions, so the team can adapt without losing responsibility or history.
What you can do: • Design and publish reusable teams visually • Run dependent, parallel, iterative, or nested delegation • Recover from browser, provider, and controller interruptions • Steer active members and answer Human Requests • Inspect one exact Result with referenced workspace files
OMS is free and self-hosted, supports Windows 11, macOS, and Linux, defaults to SQLite, and works with Codex and Claude. The core is MIT-licensed.
I’d especially value feedback on two things: 1. Is the durable parent–subagent model clear? 2. Which workflow would you try first?
Hey Product Hunt 👋
I built Oh My Subagents because starting subagents was easy, but operating them across long, consequential work was not. Parents ended up polling, reconstructing ownership from chat, and trusting provider “done” messages that did not prove the whole task was actually complete.
OMS is a local runtime for persistent, supervised Codex and Claude teams. Every team has one lead who owns the complete task and its final Result. Beneath the lead, managers own major parts of the work, delegate focused assignments, and integrate what their teammates return. Contributors complete those focused assignments and return their findings, changes, or verification.
During a run, the lead and managers choose the pattern that fits the work: sequential steps, parallel investigation, batches divided among contributors, or repeated implement–review–repair cycles—including Ralph-style loops. OMS records every assignment and return, preserves the team’s waiting and recovery state, and resumes the right owner after interruptions, so the team can adapt without losing responsibility or history.
What you can do:
• Design and publish reusable teams visually
• Run dependent, parallel, iterative, or nested delegation
• Recover from browser, provider, and controller interruptions
• Steer active members and answer Human Requests
• Inspect one exact Result with referenced workspace files
OMS is free and self-hosted, supports Windows 11, macOS, and Linux, defaults to SQLite, and works with Codex and Claude. The core is MIT-licensed.
I’d especially value feedback on two things:
1. Is the durable parent–subagent model clear?
2. Which workflow would you try first?
GitHub: https://github.com/ringlochid/oh...