oh-my-openagent v4.19.3 — Config migration you can trust
A stability-focused patch: the unified omo.jsonc config surface is now the single source of truth, migration is far more resilient across platforms, model routing got a tune-up, and CI got noticeably more deterministic.
One config, safer migration
The legacy ~/.omo/config.jsonc loader is gone — omo.jsonc is now the only config surface, and the docs walk through exactly how migration works. Migration itself got hardened where it used to bite: stale migration locks are reclaimed automatically instead of wedging startup, transform diagnostics are preserved so you can see exactly what changed, backup directories are only created when a migration actually runs, and legacy config roots are discovered correctly on Windows and in setups where your project lives outside your home directory. Codex-side config migration now flows through the same unified path.
Smarter model routing for design and creative work
The visual-engineering and artistry category chains were re-tiered, so frontend/design and creative problem-solving tasks route to the models that currently do them best.
Interaction design, grounded
Interaction and UI-behavior work is now anchored to a curated beui.dev-based reference in the shared skill library, giving agents concrete interaction patterns to draw from instead of improvising.
A calmer, more deterministic pipeline
Four flaky CI test suites were rebuilt around explicit synchronization instead of timing luck, and the release workflow itself now carries a single, binary approval gate plus a hard completion contract — releases can no longer stall half-announced.
Also included: ulw-loop planning fixes (reviewer-tier contradiction resolved, clearer team-mode decision rule).