Setup and configure oh-my-codex using current CLI behavior
Use this skill when users want to install or refresh oh-my-codex for the current project plus user-level OMX directories.
omx setup [--force] [--dry-run] [--verbose] [--scope <user|project>]
If you only want lightweight AGENTS.md scaffolding for an existing repo or subtree, use omx agents-init [path] instead of full setup.
Supported setup flags (current implementation):
--force: overwrite/reinstall managed artifacts where applicable--dry-run: print actions without mutating files--verbose: print per-file/per-step details--scope: choose install scope (user, project)omx setup performs these steps:
--scope explicit value./.omx/setup-scope.json (with automatic migration of legacy values)user)user (safe for CI/tests)dist/cli/team.js./AGENTS.md from templates/AGENTS.md (or skip when existing and no force)./.omx/hud-config.jsonomx setup only prompts for scope when no scope is provided/persisted and stdin/stdout are TTY../AGENTS.md (project root).AGENTS.md exists and --force is not used, interactive TTY runs ask whether to overwrite. Non-interactive runs preserve the file.user: user directories (~/.codex, ~/.codex/skills, ~/.omx/agents)project: local directories (./.codex, ./.codex/skills, ./.omx/agents)user scope, if historical ~/.agents/skills still exists alongside ${CODEX_HOME:-~/.codex}/skills, current setup prints a cleanup hint. Why the paths differ: ${CODEX_HOME:-~/.codex}/skills/ is the path current Codex CLI natively loads as its skill root; ~/.agents/skills/ was the skill root in an older Codex CLI release before ~/.codex became the standard home directory. OMX writes only to the canonical ${CODEX_HOME:-~/.codex}/skills/ path. When both directories exist simultaneously, Codex discovers skills from both trees and may show duplicate entries in Enable/Disable Skills. Archive or remove ~/.agents/skills/ to resolve this.project, omx launch automatically uses CODEX_HOME=./.codex unless user explicitly overrides CODEX_HOME.--force, AGENTS overwrite may still be skipped if an active OMX session is detected (safety guard).project-local) are automatically migrated to project with a one-time warning.omx setup --force --verbose
omx doctor
From omx doctor, expect:
.omx/state existsconfig.toml (~/.codex/config.toml or ./.codex/config.toml)npm run build
omx points to another install, run local entrypoint:node bin/omx.js setup --force --verbose
node bin/omx.js doctor
--force, stop active OMX session and rerun setup.