oh-my-claudecode

oh-my-claudecode is a multi-agent orchestration plugin for Claude Code. It gives Claude Code users a team-style workflow for planning, splitting, checking, and shipping work with other AI command-line agents involved. The project is branded as OMC and is distributed through the Claude Code plugin marketplace, with an npm package path for users who prefer a global CLI install. Its public site describes the current release as a plugin that coordinates Claude, Gemini CLI, and Codex CLI through specialized agents, skills, MCP-powered tools, and tmux-based worker lanes. The main value is practical orchestration. Instead of asking one model to do every part of a task, OMC lets Claude act as the conductor. Claude can break a request into stages, start worker lanes for design review, large-context reading, code review, security analysis, or architecture checks, then bring the results back into one answer. The README and site describe workflows such as autopilot, team execution, planning profiles, remote approval gates, rollback, and verification loops. That makes it useful for developers who already live in Claude Code but want a more structured way to fan out hard tasks. OMC is also opinionated about setup. Users can install it from the Claude Code plugin marketplace by adding the GitHub repository and installing the plugin, or install the npm package named oh-my-claude-sisyphus. The repository notes that the package exposes the oh-my-claudecode and omc command aliases. Setup then runs inside Claude Code with the OMC setup command or from the terminal with omc setup. The project includes documentation, a CLI reference, workflow docs, migration notes, a security guide, and release notes. The best fit is an advanced builder who uses Claude Code daily and wants repeatable agent teamwork without writing a custom orchestration harness. It is not a separate language model and it does not replace Claude Code. It wraps Claude Code with profiles, skills, automation, and worker delegation patterns. Teams should still review generated changes, watch dependency and shell access, and treat external CLI workers as separate tools with their own auth, rate limits, and failure modes. Used well, OMC turns Claude Code from a single chat loop into a more deliberate coding-agent workspace. For OpenTools readers, the key distinction is that OMC is infrastructure for agent work rather than a model benchmark entry. It belongs in a developer workflow next to terminals, pull requests, test runners, and local project state. The strongest reason to try it is not the number of bundled agents; it is the way those pieces are arranged into planning, execution, review, and rollback habits that a developer can repeat across projects.