oh-my-codex (OMX) vs. OpenAI Dots

oh-my-codex, commonly called OMX, is an open-source workflow layer that extends OpenAI Codex CLI with stronger prompts, structured development processes, runtime tooling, and agent coordination features. The project is designed for users who already work with Codex but want a more organized and durable way to manage software development tasks. OMX keeps Codex responsible for the actual agent work while adding reusable roles, skills, hooks, HUDs, team workflows, and persistent state. Its core workflow encourages users to clarify vague requests with $deep-interview, approve plans with $ralplan, and convert approved work into durable execution goals with $ultragoal. The framework also includes support for $team when coordinated parallel execution is needed and $ralph for persistent single-owner completion loops. OMX stores plans, logs, memory, runtime state, and goal artifacts inside .omx, making it easier to resume or inspect work across sessions. It supports safer development practices through named git worktrees, smoke tests, setup validation, and runtime readiness checks. The project is primarily tuned for macOS and Linux users running Codex CLI, with tmux used for the recommended durable team runtime. It also includes plugin-related support, Codex hook integration, wiki operations, repository exploration helpers, and sparkshell inspection tools. Developers can use OMX to manage complex tasks, improve context retention, organize planning, and reduce the friction of long-running Codex sessions. oh-my-codex helps technical users transform Codex into a more structured, extensible, and workflow-aware coding environment.

OpenAI Dots are always-on AI agents built to manage ongoing responsibilities and continue working on projects when the user is focused elsewhere. Powered by GPT-6 Astra, dots can proactively identify next steps, perform tasks, monitor developments, and return completed work or decisions requiring human judgment. Each dot can start with context from the user's ChatGPT memory and use Codex, connected tools, and its own cloud computer to perform work. Users decide which applications a dot can access, what responsibilities it should prioritize, and how tasks should be completed. A dot can be assigned an entire project or a smaller workflow and continue making progress between individual ChatGPT conversations. Example use cases include tracking product and revenue metrics while maintaining investor presentations, evaluating customer requirements for sales opportunities, managing API migrations, implementing software improvements based on customer feedback, and preparing content from transcripts. Dots can monitor new information as it arrives and update related work, allowing projects to remain current without requiring users to repeatedly restart the process. Users can inspect what their dot is doing, review details, provide feedback, redirect its work, or pause it whenever needed. Dots operate on independent cloud computers and support configurable permissions and Custom Rules that can allow actions, require approval, or block specific activities. Actions that could affect accounts or share information can go through Auto-review, which checks the proposed action against user instructions, Custom Rules, and safety requirements, while certain sensitive actions remain reserved for the user. Dots can be accessed through ChatGPT on web, mobile, and desktop, with availability across eligible Pro, Business Premium, and Enterprise plans and administrative enablement available for Enterprise environments.