#oh-my-codex
coterm omx launches Oh My Codex (OMX) in a coterm-aware environment. OMX is a multi-agent orchestration layer for OpenAI Codex CLI with 30+ specialized agent roles, workflow skills, and tmux-based parallel team execution. When OMX spawns team panes or HUD displays, they become native coterm splits.
#Usage
coterm omx
coterm omx --madmax --high
coterm omx teamAll arguments after omx are forwarded to the omx CLI.
#What you get
OMX's team mode and HUD use tmux for pane management. With coterm omx, those panes become native coterm splits:
- Team worker panes (Codex/Claude sessions) appear as coterm splits in the workspace
- HUD status display shows model, branch, context, and token usage in a split pane
- Auto-layout management arranges agent panes in a main-vertical grid
- Your main session stays in the primary pane while workers operate beside it
#Prerequisites
npm install -g @openai/codex oh-my-codex
omx setup
omx doctorOMX requires OpenAI Codex CLI and a working Codex auth setup. Run omx doctor to verify your installation.
#How it works
Same pattern as other coterm agent integrations. A tmux shim intercepts tmux commands from OMX and translates them into coterm API calls.
- Creates a tmux shim at ~/.coterm/omx-bin/tmux that redirects to coterm __tmux-compat
- Sets TMUX and TMUX_PANE to simulate a tmux session
- Prepends the shim directory to PATH
- Execs into omx with all remaining arguments forwarded
#Directories
| Path | Purpose |
|---|---|
~/.coterm/omx-bin/ | Contains the tmux shim script |
~/.coterm/tmux-compat-store.json | Persistent storage for tmux-compat buffers and hooks |
#Environment variables
| Variable | Purpose |
|---|---|
TMUX | Fake tmux socket path encoding the current coterm workspace and pane |
TMUX_PANE | Fake tmux pane identifier mapped to the current coterm pane |
COTERM_SOCKET_PATH | Path to the coterm control socket for the shim to connect to |