Package rename from oh-my-opencode to oh-my-openagent breaks existing configurations

[seungmun]

Description

After the package was renamed from oh-my-opencode to oh-my-openagent (v3.11.0, 2026-03-07), existing OpenCode configurations that reference the old package name silently fail to load the plugin.

The rename itself happened ~18 days ago, but both npm packages (oh-my-opencode and oh-my-openagent) have been dual-published at the same version since then. Despite this, at some point the old oh-my-opencode package stopped loading correctly in OpenCode — without any error message or warning.

Key Symptom: Silent Failure with Clean Doctor Output

Running bunx oh-my-opencode doctor --verbose reports everything as normal — no errors, no warnings. Yet the plugin simply does not load at startup. There is zero indication that the package name change is the cause. The user has to independently discover the rename by visiting the GitHub repo and noticing "previously oh-my-opencode" in the description.

Steps to Reproduce

1. Have oh-my-opencode configured in ~/.config/opencode/opencode.json:

   {
     "plugin": ["oh-my-opencode@latest"]
   }

2. Start OpenCode
3. Plugin fails to load — no error, no warning
4. Run bunx oh-my-opencode doctor --verbose — reports clean, no issues found
5. User is left with no clue why the plugin isn't working

Expected Behavior

At minimum one of:

• bunx oh-my-opencode doctor should detect and warn about the package rename
• The old npm package name (oh-my-opencode) should show a deprecation notice pointing to oh-my-openagent
• OpenCode startup should surface a clear error when a configured plugin fails to load

Actual Behavior

Plugin silently fails to load. Doctor reports clean. Users have to manually discover the rename by visiting the GitHub repo.

Workaround (Confirmed Working)

Edit ~/.config/opencode/opencode.json and change the plugin name:

{
  "plugin": [
-   "oh-my-opencode@latest"
+   "oh-my-openagent@latest"
  ]
}

Restart OpenCode. Plugin loads normally.

Context

• The rename happened in v3.11.0 (2026-03-07) per release notes: "This is a first release as an oh-my-openagent"
• Both oh-my-opencode (184 versions, 108K weekly downloads) and oh-my-openagent (9 versions, 4.8K weekly downloads) are currently published on npm
• Related issues: Plugin still displays as "oh-my-opencode" in OpenCode status bar — npm package name and hardcoded references not updated #2749 (status bar still shows old name), [Bug]: oh-my-openagent cannot recognize oh-my-openagent.jsonc, it still needs to use oh-my-opencode.jsonc #2624 (config file name not recognized)
• The old oh-my-opencode npm package has no deprecation notice

Suggested Fix

1. Add rename detection to doctor — if running as oh-my-opencode, warn the user to switch to oh-my-openagent
2. Deprecate the old npm package — npm deprecate oh-my-opencode "Renamed to oh-my-openagent. Update your opencode.json plugin entry."
3. Surface plugin load failures — OpenCode (or the plugin itself) should log when a configured plugin fails to initialize, rather than silently swallowing the error

[code-yeongyu]

The code already handles this:

1. Config file migration: detectPluginConfigFile() searches both oh-my-opencode.json and oh-my-openagent.json, and migrateLegacyConfigFile() auto-copies legacy config to the canonical name on load.

2. Doctor warning: checkSystem() detects when oh-my-opencode is still in the plugin entry and shows a warning with the exact fix: 'Update your opencode.json plugin entry: oh-my-opencode → oh-my-openagent'.

The npm deprecate notice is outside the codebase scope — that requires an npm publish action.