You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report! The grey prompt border in your screenshot is a useful clue. The border only turns your agent's colour after the agents have loaded from OpenCode's background server. If they never load, Enter (submit) and Shift+Tab (switch agent) won't do anything either. So the background server may not be finishing startup, and reinstalling an older version wouldn't fix that if the old server or its state is still around.
To narrow it down, could you share:
Operating system, how you installed OpenCode (npm, curl script, Homebrew, …) and which terminal you use (plus tmux/WSL if relevant).
The output of opencode --version and opencode service status.
Whether running opencode service restart and then opening opencode again fixes it.
The output of opencode debug agents.
The most recent log file from the folder printed by opencode debug paths log. The end of the log from a session where it got stuck is enough; please remove anything sensitive first.
Whether it happens in every project folder or only one.
You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
These issues may be related, ordered from most to least likely:
Thanks for the details, that helps a lot. The key result is opencode debug agents returning []. OpenCode always ships built-in agents (build, plan, …), so an empty list means the background server either never finished loading your projects, or your configuration is removing or breaking every agent. With no agent loaded, the grey border and the dead Enter and Shift+Tab are exactly what you'd expect. So this isn't a keyboard or terminal problem.
A few more things would narrow it down:
The output of opencode debug config. Please check it for secrets before posting, even though it's redacted.
Whether agents show up in an empty folder, e.g. in Git Bash:
Whether it works with your global config temporarily moved aside. Rename the global config folder (most likely C:\Users\<you>\.config\opencode), then run opencode service restart and opencode again. If that fixes it, please share the config files and anything in its agents/ folder (with secrets removed), then rename the folder back.
A fresh log from a run where it gets stuck. The logs you posted are from June (that one is from OpenCode v1) and from 9 October in another project, so they don't show this failure. Please run opencode service restart, open opencode until it's stuck, then post the last ~100 lines of opencode.log from the folder printed by opencode debug paths log, especially any level=WARN or level=ERROR lines.
Thanks for the details, that helps a lot. The key result is opencode debug agents returning []. OpenCode always ships built-in agents (build, plan, …), so an empty list means the background server either never finished loading your projects, or your configuration is removing or breaking every agent. With no agent loaded, the grey border and the dead Enter and Shift+Tab are exactly what you'd expect. So this isn't a keyboard or terminal problem.
A few more things would narrow it down:
The output of opencode debug config. Please check it for secrets before posting, even though it's redacted.
Whether agents show up in an empty folder, e.g. in Git Bash:
mkdir -p /tmp/oc-test && cd /tmp/oc-test && opencode debug agents
Whether it works with your global config temporarily moved aside. Rename the global config folder (most likely C:\Users\<you>\.config\opencode), then run opencode service restart and opencode again. If that fixes it, please share the config files and anything in its agents/ folder (with secrets removed), then rename the folder back.
A fresh log from a run where it gets stuck. The logs you posted are from June (that one is from OpenCode v1) and from 9 October in another project, so they don't show this failure. Please run opencode service restart, open opencode until it's stuck, then post the last ~100 lines of opencode.log from the folder printed by opencode debug paths log, especially any level=WARN or level=ERROR lines.
Plugins like opencode-supermemory and opencode-browser were developed for OpenCode v1
(opencode-ai).
• In OpenCode v2 (@opencode/cli 2.0.28), plugins require a new Effect-TS export format (default
definition with id and effect/setup function). These older plugins will fail to initialize until
updated for v2.
btw you are a coding assistant for opencode team ? are you built on top of opencode or openclaw ? i also want to intall a agent like u on my repos , do team have oss repo of yours ?
Thanks for tracking that down! I tried to reproduce it on Linux with @opencode/[email protected] and "plugin": ["opencode-supermemory", "opencode-browser"], in both a project opencode.json and the global config:
opencode-browser fails to load, but only logs a warning: failed to load plugin … Plugin must export a default definition with an id and an effect or setup function. That's expected, since it was written for v1.
opencode-supermemory loads without an error.
opencode debug agents still lists the built-in agents (build, plan, …), and the prompt works.
So on Linux, an incompatible v1 plugin doesn't leave OpenCode with no agents the way it did for you. To find what's different on your side, could you share:
Your config file with the plugin entries (secrets removed), and whether the problem goes away when you remove onlyopencode-browser, or onlyopencode-supermemory.
The level=WARN / level=ERROR lines from opencode.log (in the folder printed by opencode debug paths log) from a run where it was stuck, especially any failed to load plugin lines.
We already have issues about v1 plugins not loading in v2: #48138 (backward compatibility for v1 plugins) and #48365.
Closing this for now, since we haven't heard back. I couldn't reproduce it on Linux with 2.0.28: with opencode-supermemory and opencode-browser configured, the v1 plugin that couldn't load (opencode-browser) only logged a warning, and the built-in agents still loaded. To find out why every agent vanished on your Windows setup, I'd need your plugin config, which plugin causes it on its own, and the level=WARN / level=ERROR lines from opencode.log from a run where it got stuck.
If it happens again, reply with those details and we can reopen this. For v1 plugins not loading in v2 in general, see #48138 and #48365. Thanks for tracking down the plugin cause!
Activity
opencode-agent commentedon Oct 13, 2026
Thanks for the report! The grey prompt border in your screenshot is a useful clue. The border only turns your agent's colour after the agents have loaded from OpenCode's background server. If they never load, Enter (submit) and Shift+Tab (switch agent) won't do anything either. So the background server may not be finishing startup, and reinstalling an older version wouldn't fix that if the old server or its state is still around.
To narrow it down, could you share:
opencode --versionandopencode service status.opencode service restartand then openingopencodeagain fixes it.opencode debug agents.opencode debug paths log. The end of the log from a session where it got stuck is enough; please remove anything sensitive first.You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
These issues may be related, ordered from most to least likely:
Sahil-Gupta584 commentedon Oct 13, 2026
user@DESKTOP-1VKI4SO MINGW64 /c/s/opencmo (main)
$ opencode debug agents
[]```
logs of opencode.log>
opencode-agent commentedon Oct 13, 2026
Thanks for the details, that helps a lot. The key result is
opencode debug agentsreturning[]. OpenCode always ships built-in agents (build,plan, …), so an empty list means the background server either never finished loading your projects, or your configuration is removing or breaking every agent. With no agent loaded, the grey border and the dead Enter and Shift+Tab are exactly what you'd expect. So this isn't a keyboard or terminal problem.A few more things would narrow it down:
opencode debug config. Please check it for secrets before posting, even though it's redacted.C:\Users\<you>\.config\opencode), then runopencode service restartandopencodeagain. If that fixes it, please share the config files and anything in itsagents/folder (with secrets removed), then rename the folder back.opencode service restart, openopencodeuntil it's stuck, then post the last ~100 lines ofopencode.logfrom the folder printed byopencode debug paths log, especially anylevel=WARNorlevel=ERRORlines.Possibly related, ordered by likelihood:
coloruses a v1 theme name such asaccentorprimary. If you have custom agent files, this is worth checking.Sahil-Gupta584 commentedon Oct 13, 2026
i foudn the issue
Plugins like opencode-supermemory and opencode-browser were developed for OpenCode v1
(opencode-ai).
• In OpenCode v2 (@opencode/cli 2.0.28), plugins require a new Effect-TS export format (default
definition with id and effect/setup function). These older plugins will fail to initialize until
updated for v2.
btw you are a coding assistant for opencode team ? are you built on top of opencode or openclaw ? i also want to intall a agent like u on my repos , do team have oss repo of yours ?
opencode-agent commentedon Oct 13, 2026
Thanks for tracking that down! I tried to reproduce it on Linux with
@opencode/[email protected]and"plugin": ["opencode-supermemory", "opencode-browser"], in both a projectopencode.jsonand the global config:opencode-browserfails to load, but only logs a warning:failed to load plugin … Plugin must export a default definition with an id and an effect or setup function. That's expected, since it was written for v1.opencode-supermemoryloads without an error.opencode debug agentsstill lists the built-in agents (build,plan, …), and the prompt works.So on Linux, an incompatible v1 plugin doesn't leave OpenCode with no agents the way it did for you. To find what's different on your side, could you share:
pluginentries (secrets removed), and whether the problem goes away when you remove onlyopencode-browser, or onlyopencode-supermemory.level=WARN/level=ERRORlines fromopencode.log(in the folder printed byopencode debug paths log) from a run where it was stuck, especially anyfailed to load pluginlines.We already have issues about v1 plugins not loading in v2: #48138 (backward compatibility for v1 plugins) and #48365.
To your other question: I'm an automated triage assistant the OpenCode team runs on this repository. I can't say whether it's published as a separate project. If you want OpenCode working as an agent on your own repositories, see the GitHub integration docs: https://opencode.ai/docs/github
opencode-agent commentedon Oct 16, 2026
Closing this for now, since we haven't heard back. I couldn't reproduce it on Linux with 2.0.28: with
opencode-supermemoryandopencode-browserconfigured, the v1 plugin that couldn't load (opencode-browser) only logged a warning, and the built-in agents still loaded. To find out why every agent vanished on your Windows setup, I'd need your plugin config, which plugin causes it on its own, and thelevel=WARN/level=ERRORlines fromopencode.logfrom a run where it got stuck.If it happens again, reply with those details and we can reopen this. For v1 plugins not loading in v2 in general, see #48138 and #48365. Thanks for tracking down the plugin cause!