Migration

Cross-version migration notes for OMX — removed prompts, renamed skills, and setup changes between major versions.

This page tracks breaking changes and migration steps between OMX versions. Start here when upgrading to a new major or minor version and consult the changelog for the full release history.

Post-v0.4.4 mainline

The post-v0.4.4 mainline merged catalog consolidation, setup scope changes, and tmux hardening. The full upstream guide is at docs/migration-mainline-post-v0.4.4.md.

Removed prompts

deep-executor — use /prompts:executor instead.
scientist — use /prompts:researcher for 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 in config are auto-migrated. Verify with:

omx help | grep -e "--scope"

Verification checklist

After upgrading, confirm removed references are gone:

rg -n "deep-executor|scientist|pipeline|project-session-manager|ultrapilot" \
  README.md docs scripts .omx -S

Validate team health:

omx doctor --team

General upgrade steps

Pull the latest version: npm install -g oh-my-codex (or your install method).
Run omx doctor to check for configuration issues.
Run omx setup if the doctor reports missing prompts or skills.
Check this page and the changelog for version-specific steps.

Changelog — full release history
Configuration — config files affected by migrations

Was this page helpful?

Edit this page Report an issue