Who it is forA developer with several agent subscriptions who wants them reviewing or building in parallel.
The problemSwitching between agent CLIs by hand wastes time and loses the shared context.
The outcomeParallel tmux workers from different providers on the same task, with status and shutdown commands.
What you need first
- Claude Code
- npm for the CLI path (oh-my-claude-sisyphus)
- tmux and the Codex or Gemini CLIs for terminal team workers
- Linux with flock for named autopilot stage profiles
Steps
- Run
npm i -g oh-my-claude-sisyphus@latestandomc setup - Run
omc team 2:codex "review auth module for security issues"with your own task - Add a worker from another provider, for example
omc team 1:claude "implement the payment flow" - Check progress with omc team status and stop with omc team shutdown
- Inside Claude Code, use
/team 3:executor "fix all TypeScript errors"for the native team pipeline
Prompt for your agent
Install the Yeachan-Heo/oh-my-claudecode CLI, then run omc team with 2 codex workers to review <module> for security issues and 1 claude worker to implement <fix>. Report each worker's findings.
Caveat. Claude Code native teams need CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS set to 1 in ~/.claude/settings.json; without it OMC falls back to non-team execution.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Yeachan-Heo/oh-my-claudecode and "Run Codex, Gemini and Claude workers in parallel with omc team"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer