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
{{ message }}
Repository navigation
Opencode Desktop on Windows does not show any models, providers, or previous chat history on startup. #23011
After updating Opencode Desktop (Windows) to versions 1.4.5, 1.4.6, and 1.4.7, the app does not load properly on startup.
Specifically:
Models are not displayed
Providers are not displayed
Previous conversation history is missing
It is not possible to start a new conversation
The application eventually recovers and works normally again, but only after waiting for roughly 30 minutes.
Expected behavior
The app should load models, providers, and chat history normally on startup, and conversations should be available immediately.
Actual behavior
On startup, models, providers, and chat history are missing, and chatting is unavailable. The issue resolves itself only after a long loading time of around 30 minutes.
Reproduced on macOS arm64 with v1.14.35 (different version line from OP, same symptom).
Symptom
Fresh install on macOS, login completed via CLI (opencode auth login)
opencode auth list and opencode web both show all credentials/providers correctly
Desktop app: 接続済みプロバイダー empty, 人気のプロバイダー shows only "Custom" - never recovers (waited 30+ min)
Workaround that worked immediately
Setting OPENCODE_PURE=true causes the desktop to skip external plugin loading, and providers list populates immediately:
launchctl setenv OPENCODE_PURE true
open /Applications/OpenCode.app
asar source confirmation
From out/main/chunks/node-BgdKCufl.js:
if(Flag.OPENCODE_PURE&&cfg3.plugin_origins?.length){log50.info("skipping external plugins in pure mode",{count: cfg3.plugin_origins.length});}
My plugin config
~/.config/opencode/config.json:
{ "plugin": ["opencode-notification@latest"] }
~/.config/opencode/package.json requested @opencode-ai/plugin: 1.4.3 while bun.lock had 1.3.13 - version drift between desired and locked likely triggers an npm install retry that blocks UI init.
Conclusion
Same root cause as @ronnyf's Linux logs - external plugin install/resolution hangs UI initialization. Affects the v1.14.x line on macOS as well, not only v1.4.x on Windows/Linux.
Activity
github-actions commentedon Apr 17, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct from the above, please let us know how it differs.
Lazarus-glhf commentedon Apr 18, 2026
Still happened on 1.4.11
ronnyf commentedon Apr 18, 2026
it seems to be related to loading plugins, I tried adding:
and get this in the logs:
or
szkhr1025 commentedon May 5, 2026
Reproduced on macOS arm64 with v1.14.35 (different version line from OP, same symptom).
Symptom
opencode auth login)opencode auth listandopencode webboth show all credentials/providers correctlyWorkaround that worked immediately
Setting
OPENCODE_PURE=truecauses the desktop to skip external plugin loading, and providers list populates immediately:launchctl setenv OPENCODE_PURE true open /Applications/OpenCode.appasar source confirmation
From
out/main/chunks/node-BgdKCufl.js:My plugin config
~/.config/opencode/config.json:{ "plugin": ["opencode-notification@latest"] }~/.config/opencode/package.jsonrequested@opencode-ai/plugin: 1.4.3whilebun.lockhad1.3.13- version drift between desired and locked likely triggers an npm install retry that blocks UI init.Conclusion
Same root cause as @ronnyf's Linux logs - external plugin install/resolution hangs UI initialization. Affects the v1.14.x line on macOS as well, not only v1.4.x on Windows/Linux.
aliakseiz commentedon May 16, 2026
Confirming what @ronnyf said: when there are no plugins in the config, the Linux desktop application starts normally.
Adding
or any other plugin, causes "Failed to load sessions for X".
v1.15.1
Rolling back to any of v14.x versions doesn't help. Didn't try the v13.x.
github-actions commentedon Jul 16, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
jigyasha792 commentedon Sep 29, 2026
the issue still persists.