Problem: Abnormal behavior/config conflicts after OMC upgrade —— Trove problem library

What you will run into

After upgrading, behavior is abnormal, configs conflict, commands error out. Can't change anything, can't run anything, and don't know what's wrong.

Why this happens

Version-to-version config/migration differences and old config leftovers — after the upgrade, old config doesn't match the new version and behavior goes haywire.

"Abnormal behavior after an upgrade" is almost always config schema drift: the new version changed the field structure or semantics of the config (for example, a rule changed from "applies globally" to "applies per project"), while the config on disk is still in the old format.

The tool does not auto-migrate unknown fields — it keeps reading what it can and silently ignores the rest, which is why "config is still there, but behavior changed" feels so weird.

omc-doctor turns that silent ignoring into an explicit report: it checks config, version, and environment item by item and lists the mismatches, saving you the effort of diffing old and new docs line by line.

So after an upgrade, run the diagnostic first — it is faster than reading the changelog.

Step by step

1. Run omc-doctor — Required

omc-doctor

Built-in diagnostics that point straight at the problem (CSDN 2026-04 case path).

2. Fix config per the diagnostic — Diagnose

Reinstall to align versions if needed:

npm i -g oh-my-claude-sisyphus@5.0.0

3. Keep the diagnostic output when reporting — Diagnose

omc-doctor output includes the version number and node version; attach them when reporting issues.

How to confirm it works

Diagnostic clean (expected shape):

omc-doctor → all checks pass / no ERROR

Commands behave normally again.

Other environments

Symptom

Behavior anomalies after upgrade, config conflicts, command errors.

Cause

Config/migration differences between versions; stale leftover config.

Solution

1. Run omc-doctor (built-in diagnostics) to find the problem.
2. Fix config per the diagnostics; if needed reinstall npm i -g oh-my-claude-sisyphus@5.0.0 to align versions.
3. Keep the omc-doctor output when reporting issues (include version and node version).