[BUG] oh-my-openagent works on 1.3.13 but registers nothing on 1.3.14

Description

After upgrading OpenCode from 1.3.13 to 1.3.14, oh-my-openagent becomes unusable.

This does not look like a simple “plugin file not found” failure. Based on the startup logs, the plugin still enters the loading flow, but then ends up registering nothing.

Rolling back to 1.3.13 restores normal behavior on the same machine/config.

Relevant log symptom from the plugin log:

Loaded 0 plugins with 0 commands, 0 skills, 0 agents, 0 MCP servers

At the same time, the main OpenCode log still shows plugin loading, for example:

service=plugin path=oh-my-opencode loading plugin

So the regression appears to be: plugin loading starts, but plugin-side registration/discovery becomes empty on 1.3.14.

Plugins

oh-my-openagent (logs still reference legacy path/name oh-my-opencode)

OpenCode version

Broken: 1.3.14
Works: 1.3.13

Steps to reproduce

Install/use OpenCode 1.3.14
Enable oh-my-openagent in the local OpenCode config
Start OpenCode
Observe that OMO-provided commands / skills / agents are missing or unusable
Check logs and see plugin loading begins, but plugin registration result is empty
Downgrade to 1.3.13
Observe that the same plugin/config works again

Screenshot and/or share link

No share link yet. Relevant local logs:

OpenCode logs: /home/cc/.local/share/opencode/log/
Plugin log: /tmp/oh-my-opencode.log

Operating System

WSL2 Linux (Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 GNU/Linux)

Terminal

xterm-256color inside WSL

Seems related #gyp path at

export OPENCODE_DISABLE_AUTOUPDATE=1

opencode upgrade v1.3.13

Seems like caused:

fix for this going out in 10min

In dax we trust 🙏

fix for this going out in 10min

Can confirm, works now

not working for me, OMO still missing

not working for me, OMO still missing

~~same~~

It works.

not working for me, OMO still missing

Restart opencode couple of times. Its installing dependencies in background

is it good in 3.1.15?

i tested and it worked for me

is it good in 3.1.15?

works now, thx

I got the same issues, I already use opencode version 1.3.17 on wsl, and it still can not load oh my openagent plugin, even though I've installed and reinstalled it countless times. plz, let's take a look

is it good in 3.1.15?

It is still not good on mac. I just opened opencode to check. Is there anything else I need to do to make it good again?

For now i am opencode upgrade v1.3.13

我遇到了同样的问题，我已经在WSL上用OpenCode 1.3.17版本了，但它依然无法加载我的openagent插件，尽管我已经无数次安装和重装了。请，我们来看看

+1
I encountered the same problem on Windows 11.

I have encountered the same issue. On the macOS, with OpenCode version 1.3.17, I still cannot load the Oh My Opencode plugin.

Environment: Windows 11, OpenCode 1.3.17, oh-my-openagent 3.15.3

Timeline: Was working fine on 1.3.15 before holiday. After returning, OpenCode auto-updated to 1.3.17 and OMO agents (Sisyphus, etc.) disappeared from the UI. Only default build/plan agents were shown.

Diagnosis: bunx oh-my-opencode doctor --verbose showed plugin 3.15.3 loaded with all checks passing, but OpenCode TUI still failed to surface OMO agents.

Workaround that fixed it: Changed plugin entry in opencode.json from:

"plugin": ["oh-my-openagent@latest"]

to local file path:

"plugin": ["file:///C:/Users/Administrator/.cache/opencode/packages/oh-my-openagent@latest/dist/index.js"]

After restart, all OMO agents loaded correctly.

Note: My home PC (also Windows, same "oh-my-openagent@latest" plugin entry) loads OMO agents normally. Both machines have the same plugin config, so the issue appears to be machine-specific — likely related to the local plugin cache/install state rather than the config format itself.

我遇到了相同问题。+1

Environment: Windows 11, OpenCode 1.3.17, oh-my-openagent 3.15.3

Timeline: Was working fine on 1.3.15 before holiday. After returning, OpenCode auto-updated to 1.3.17 and OMO agents (Sisyphus, etc.) disappeared from the UI. Only default build/plan agents were shown.

Diagnosis: bunx oh-my-opencode doctor --verbose showed plugin 3.15.3 loaded with all checks passing, but OpenCode TUI still failed to surface OMO agents.

Workaround that fixed it: Changed plugin entry in opencode.json from:

"plugin": ["oh-my-openagent@latest"]
to local file path:

"plugin": ["file:///C:/Users/Administrator/.cache/opencode/packages/oh-my-openagent@latest/dist/index.js"]
After restart, all OMO agents loaded correctly.

Note: My home PC (also Windows, same "oh-my-openagent@latest" plugin entry) loads OMO agents normally. Both machines have the same plugin config, so the issue appears to be machine-specific — likely related to the local plugin cache/install state rather than the config format itself.

Very useful advice.

I asked my own OpenCode setup to diagnose the issue autonomously, and it eventually succeeded in loading oh-my-opencode on OpenCode 1.3.17.(the stable version works well with omo v3.15.3)
That suggests there is at least a temporary workaround for this issue.
Based on that investigation, I confirmed that the plugin can still work on 1.3.17, and I documented the workaround that made it load successfully in my environment.

Working workaround for oh-my-openagent / oh-my-opencode load issues on OpenCode 1.3.13+

I hit the same plugin-loading problem reported by others after OpenCode 1.3.13+, especially around 1.3.15, and I also reproduced the newer 1.4.0 plugin install failure.
After testing this locally, I found that the plugin itself was not the main problem. The more immediate issue was OpenCode's remote npm plugin installation path.
This workaround made the plugin load successfully for me.

What is going wrong?

There appear to be two related problems:

On OpenCode 1.3.15, oh-my-openagent / oh-my-opencode may fail to load agents or hang at startup.
On OpenCode 1.4.0, plugin installation can fail with:

fetch() proxy.url must be a non-empty string

In practice, this means OpenCode may fail before the plugin is actually available, so the runtime falls back to the default agent.

Main idea of the workaround

Instead of letting OpenCode install the plugin from npm by itself, install the plugin manually with npm, then point OpenCode directly to the local plugin directory.
This bypasses OpenCode's broken remote plugin install path.

Exact steps

Step 1. Install the plugin manually with npm

Run:

npm install --prefix ~/.config/opencode oh-my-openagent@v3.15.3

What each part means

npm install
- Tells npm to install a package.
--prefix ~/.config/opencode
- Tells npm to treat ~/.config/opencode as the install target directory.
- This means npm will create or update:
  - ~/.config/opencode/package.json
  - ~/.config/opencode/package-lock.json
  - ~/.config/opencode/node_modules/
oh-my-openagent@latest
- Installs the latest version of the plugin package.
- I used the renamed package identity here because current docs prefer oh-my-openagent.

What this step should produce

After this command, the plugin should exist at:

~/.config/opencode/node_modules/oh-my-openagent

That local directory is the key to the workaround.

Step 2. Edit `~/.config/opencode/opencode.json`

If your config currently looks like this:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "oh-my-openagent"
  ]
}

change it to this:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "/home/YOUR_USERNAME/.config/opencode/node_modules/oh-my-openagent"
  ]
}

What each line means

"plugin": [
- This starts the list of plugins that OpenCode should load.
"/home/YOUR_USERNAME/.config/opencode/node_modules/oh-my-openagent"
- This is the important part.
- Instead of telling OpenCode to download the plugin by package name, this tells OpenCode to load the plugin directly from a local filesystem path.
- This avoids the broken npm/arborist/Bun install path entirely.

Important note

Use the full absolute path.
Do not rely on this form inside JSON:

"~/.config/opencode/node_modules/oh-my-openagent"

because ~ is a shell feature, not guaranteed JSON path expansion.

Step 3. Rename the plugin config file to the new preferred name

If you already have an old config file like this:

~/.config/opencode/oh-my-opencode.json

rename or copy it to:

~/.config/opencode/oh-my-openagent.json

For example:

mv ~/.config/opencode/oh-my-opencode.json ~/.config/opencode/oh-my-openagent.json

What this command does

mv
- Moves or renames a file.
~/.config/opencode/oh-my-opencode.json
- The old legacy plugin config filename.
~/.config/opencode/oh-my-openagent.json
- The new preferred plugin config filename.
  Why this matters

The compatibility layer still recognizes old names, but current docs prefer:

plugin entry: oh-my-openagent
plugin config file: oh-my-openagent.json or oh-my-openagent.jsonc
So renaming reduces compatibility-edge confusion.

Why this workaround helps

OpenCode's failing path is:

read plugin name from opencode.json
try to fetch/install it from npm internally
fail in the npm/arborist/Bun path
plugin never becomes available
built-in default agent gets used instead
The workaround changes that flow to:
install plugin yourself with normal npm
point OpenCode directly to the already-installed local plugin directory
OpenCode loads the plugin from disk
no broken remote install step is needed

Conclusion

If oh-my-openagent or oh-my-opencode is not loading on OpenCode 1.3.15+, or if OpenCode 1.4.0 fails with:

fetch() proxy.url must be a non-empty string

this worked for me:

install the plugin manually with npm
point plugin to the local installed directory
rename plugin config to oh-my-openagent.json

This is currently the most reliable workaround I found until OpenCode fixes the remote npm plugin installation path.

i meet same problem，if oh my opencode is important plugin，i think should support version match map between opencode and oh my opencode

same here, all agents from OMO were gone, and I came back specifically to share my situation. At first I tried reinstalling again and again, but in vain, which is very annoying. In order not to delay my main stuff, I installed oh-my-opencode-slim as a temporary replacement. Days later, I tried this and figured this out, maybe it will work for someone else. Firstly I searched all relevant files and directories, like oh-my-opencode and oh-my-openagent, which were "everywhere" on my computer. After that I deleted all those files and directories in the search results, ran bunx oh-my-openagent install, got all my agents back. Plus, here's my version, OpenCode 1.15.6, first prompt would come out "OhMyOpenCode 4.4.0 Sisyphus on steroids is steering OpenCode."

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

[BUG] oh-my-openagent works on 1.3.13 but registers nothing on 1.3.14 #21032

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

7 remaining items

Working workaround for oh-my-openagent / oh-my-opencode load issues on OpenCode 1.3.13+

What is going wrong?

Main idea of the workaround

Exact steps

Step 1. Install the plugin manually with npm

Step 2. Edit `~/.config/opencode/opencode.json`

Step 3. Rename the plugin config file to the new preferred name

Why this workaround helps

Conclusion

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] oh-my-openagent works on 1.3.13 but registers nothing on 1.3.14 #21032

Description

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

tiamed commented on Apr 4, 2026

code-lixm commented on Apr 4, 2026

thdxr commented on Apr 4, 2026

jurij commented on Apr 4, 2026

jurij commented on Apr 4, 2026

stevenpi140 commented on Apr 4, 2026

IlluminateDarkheat commented on Apr 4, 2026

jurij commented on Apr 4, 2026

thdxr commented on Apr 4, 2026

thdxr commented on Apr 4, 2026

stevenpi140 commented on Apr 4, 2026

7 remaining items

anhalu commented on Apr 6, 2026

b4-io commented on Apr 7, 2026

girvs commented on Apr 7, 2026

JohnYehyo commented on Apr 7, 2026

XIYBHK commented on Apr 7, 2026

shilei19 commented on Apr 8, 2026

Goodboy-dai commented on Apr 8, 2026

Working workaround for oh-my-openagent / oh-my-opencode load issues on OpenCode 1.3.13+

What is going wrong?

Main idea of the workaround

Exact steps

Step 1. Install the plugin manually with npm

Step 2. Edit ~/.config/opencode/opencode.json

Step 3. Rename the plugin config file to the new preferred name

Why this workaround helps

Conclusion

chenwuxing commented on Apr 20, 2026

Jason6987 commented on May 25, 2026

github-actions commented on Jul 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Step 2. Edit `~/.config/opencode/opencode.json`