omx-setup

Automating oh-my-codex installation for a local codebase involves resolving the project scope, creating necessary OMX directories, and installing prompts plus agent configs. This process ensures scope resolution and config merging to prevent manual setup drift across environments.

OMX setup is an automated installation process for oh-my-codex that manages prompts, agent configs, and skills across project and user scopes. You need it when configuring a local codebase or onboarding teams to ensure consistent directory creation and artifact installation.

Yes, you can install agent configs and prompts for both project and user scopes. The setup process resolves and persists installation scope with sensible defaults, ensuring artifacts are correctly installed and merged into config.toml for each specific level.

To generate an AGENTS.md file and maintain OMX state, run the OMX setup command to refresh the project root file. This ensures verification markers exist and the installation state is accurately persisted within your local codebase environment.

The best way to prevent configuration drift when onboarding teams to OMX is to automate the installation and refresh of user-level OMX directories. This merges config.toml files and ensures scope resolution stays consistent across all developer environments.

OMX setup may fail to merge config.toml correctly if installation scope resolution encounters conflicts or missing directories. Ensuring proper directory creation and artifact installation before merging configurations helps maintain accurate OMX state and verification markers.