Uh oh!
There was an error while loading. Please reload this page.
Fix plugin agent registration issue - #25505
Conversation
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found one potentially related PR: Related PR:
The search results primarily return PR #25505 (the current PR) itself, which indicates this is a unique fix. The only other potentially related PR is #25466, which deals with plugin initialization sequencing. No clear duplicate PRs found - this appears to be addressing a specific plugin agent registration bug without direct overlaps in scope. |
rekram1-node
commented
May 3, 2026
already fixed, thanks for helping tho |
Issue for this PR
Closes#25441
Type of change
What does this PR do?
External plugins were being loaded, but agents provided by those plugins were not available in the agent selector.
This PR fixes the plugin agent registration path so agents from plugin modules are registered before the agent list is resolved. With this change, installing a plugin such as
oh-my-opencode@3.17.12correctly makes its agents available in the TUI.I verified this by loading the plugin locally and confirming that its agents appeared in the agent selector.
How did you verify your code works?
Tested locally on Windows from the opencode repository.
I configured the plugin in
.opencode/opencode.jsonc:{ "plugin": ["oh-my-opencode@3.17.12"] }Then I started opencode and confirmed the plugin was loaded:
I also verified that:
/agentrequest completes successfullybun run --cwd packages/opencode typecheckpassesScreenshots / recordings
Plugin-provided agents now appear in the agent selector.
Checklist