Oh-My-ClaudeCode (OMC) is a multi-agent orchestration layer for Claude Code, Anthropic's AI coding assistant. It extends Claude Code with a plugin system, custom MCP tools, a team collaboration engine, a real-time HUD, and a rich hook system. The system is implemented in TypeScript and runs as a CLI tool (`omc`), an npm package (`oh-my-claude-sisyphus`), and a Claude Code plugin. It manages autonomous coding pipelines (autopilot, ralph), multi-worker team sessions via tmux, skill learning and injection, and provides extensive tooling including LSP integration, AST analysis, Python REPL, and git-based checkpoints. Architecturally, OMC is a modular monolith with clear separation: a CLI entry point (Commander-based), a hook registry with ~20+ lifecycle hooks (session-end, pre-tool-use, persistent-mode, etc.), a team subsystem with state machines and tmux-based worker management, a HUD rendering engine, and a standalone MCP server exposing 33+ tools. The system integrates with multiple AI providers (Claude, Codex, Gemini, Grok, Cursor) and git hosting providers (GitHub, GitLab, Azure DevOps, Bitbucket, Gitea). External dependencies include `@anthropic-ai/claude-agent-sdk`, `@modelcontextprotocol/sdk`, `better-sqlite3`, `zod`, and `commander`. Key data flows include: user input → CLI or Claude Code hook → hook dispatcher → feature modules (autopilot, team, skills) → tool execution → state persistence (filesystem, SQLite). The system maintains extensive state on disk (`.omc/state/`, session transcripts, team events, skill files) and uses file-based locking for concurrency safety. The JEV shadow judgment system provides non-blocking evaluation of heuristic decisions against an external API for quality monitoring. The codebase demonstrates strong engineering practices: extensive test coverage (~3000+ tests), modular architecture with clear interfaces, atomic file operations, and security-conscious utilities (SSRF guard, token redaction, path traversal prevention). It is actively maintained with frequent releases and responsive issue triage.

oh-my-codex is a multi-agent orchestration CLI tool extending OpenAI Codex with team coordination, workflow automation, and persistent infrastructure. It provides a command-line interface (omx) and a suite of native Rust binaries for tasks like tmux session management (omx-mux), command family execution (omx-sparkshell), and runtime replay (omx-runtime-core). The system orchestrates AI agents through states (autopilot, ralph, team, ultragoal), manages tmux-isolated worker panes, maintains a persistent wiki knowledge base with full-text query and linting, dispatches lifecycle notifications to Discord/Telegram/webhooks, and includes a hook plugin system with an SDK for implementing custom event handlers. It also features a VSCode extension for session management and a mission-driven research workflow (autoresearch) that executes evaluator-gated experiments. Architecturally, it is a hybrid Node.js CLI application with Rust sidecar binaries. The TypeScript core (src/) implements the CLI, state machines, team coordination, MCP servers, notification engine, and extensibility framework. Rust crates provide low-level tmux interaction, command execution with language-specific registries, and a replay-capable runtime core. The system integrates deeply with Codex CLI through native hooks and plugin marketplace, and supports platform-specific behavior for macOS, Linux, and Windows. The codebase is heavily tested (hundreds of unit/integration/contract tests), uses atomic file operations for state persistence, and employs file-based locking with heartbeat for cross-process coordination. While primarily an application, it includes a small data/research component: playground demos for Bayesian optimization and ML model tuning, and the autoresearch mission framework with evaluator scripts. However, these are peripheral to the main orchestration purpose. The repository demonstrates strong engineering practices with modular design, dependency injection for testability, and clear separation of concerns across systems (auth, adapters, notifications, team state, hooks, MCP). It is actively maintained with frequent releases and extensive QA documentation.