Migration
Breaking changes and upgrade steps between OMX versions
Check this page before upgrading to a new major or minor version. For the full release history, see the changelog.
Post-v0.4.4 mainline
This version includes catalog consolidation, setup scope changes, and tmux hardening. For the full upstream guide, see docs/migration-mainline-post-v0.4.4.md.
Removed prompts
deep-executor— use/prompts:executorinsteadscientist— use/prompts:researcherfor research workflows
Removed skills
| Removed | Replacement |
|---|---|
$pipeline | $team (default orchestrator) |
$ultrapilot | $team |
$deepinit | omx agents-init [path] (CLI command) |
$psm / $project-session-manager | No in-repo replacement — remove from automation |
$release | No in-repo replacement — use your project release process |
$learn-about-omx / $learner / $writer-memory | No in-repo replacement — remove stale references |
Setup scope changes
omx setup now supports --scope user and --scope project. Legacy project-local values are migrated automatically.
omx help | grep -e "--scope"Verification checklist
After upgrading, confirm that removed references are gone:
rg -n "deep-executor|scientist|pipeline|project-session-manager|ultrapilot" \
README.md docs scripts .omx -SThen check team health:
omx doctor --teamGeneral upgrade steps
- Install the latest version:
npm install -g oh-my-codex - Run
omx doctorto check for configuration issues - Run
omx setupif the doctor reports missing prompts or skills - Check this page and the changelog for any version-specific steps
Related
- Changelog — full release history
- Configuration — config files affected by migrations