[BUG]: CLI stuck on "Loading plugins..." screen on startup on Windows

[Zohair-coder]

Description

I do not have any plugins installed. I believe it started happening after I upgraded to version 1.14.25. This issue only comes up about 50% of the time. I am unable to use Ctrl+C to exit this screen and have to close the terminal completely to restart.

Some details that may be relevant:

• I am running opencode on my work computer, which has an internal npm registry and cert configured

Plugins

None

OpenCode version

1.14.25

Steps to reproduce

Start opencode using the opencode command.

Screenshot and/or share link

Operating System

Windows 11

Terminal

Wezterm

[github-actions]

This issue might be a duplicate of an existing issue. Please check:

• Windows: opencode CLI hangs at startup when running internal npm list / npm config get registry #11657: Windows CLI hangs at startup when running internal npm list / npm config get registry — very similar symptoms (CLI stuck on startup on Windows, no error shown, must terminate manually). The internal npm registry and custom cert you mentioned at your workplace could be related to why npm commands hang during OpenCode's startup checks.

[Zohair-coder]

Downgrading to version 1.14.24 appears to have fixed the issue.

[EasonSpirit]

2026-04-27T013347.log

I also encountered this issue in the latest version (1.14.25), Out of ten launch attempts, only one starts successfully.

[Syh1906]

I found a more specific reproduction pattern for this issue.

Updated finding

This happens when I start a second OpenCode TUI in the same project directory while the first one is still running.

If I switch to a different project directory, OpenCode can open normally.

Environment

• OpenCode: 1.14.26
• OS: Windows
• Install method: npm global package opencode-ai
• Command used during debugging: opencode --print-logs
• DB size: about 4.94 GB

What I tested

1. I started opencode --print-logs in a project directory.

2. The first TUI opened successfully.

3. Without closing the first OpenCode process, I opened another terminal in the same project directory.

4. I started opencode --print-logs again.

5. The second TUI stayed on:

   Loading plugins...
   

6. I then switched to another project directory and started OpenCode there.

7. OpenCode opened normally in the other project directory.

Log observations from the second same-directory startup

The second startup does not appear to be stuck while opening the database or loading plugin files.

Relevant log lines:

INFO  2026-04-27T01:43:49 +119ms service=server-proxy directory=<project-dir> creating instance
INFO  2026-04-27T01:43:49 +4ms service=project directory=<project-dir> fromDirectory
INFO  2026-04-27T01:43:49 +235ms service=db path=<opencode-data-dir>/opencode.db opening database
INFO  2026-04-27T01:43:49 +6ms service=db count=13 mode=bundled applying migrations
INFO  2026-04-27T01:43:49 +21ms service=server-proxy directory=<project-dir> bootstrapping
INFO  2026-04-27T01:43:49 +0ms service=plugin path=file://<opencode-config-dir>/plugins/session-id-header.js loading plugin
INFO  2026-04-27T01:43:49 +0ms service=plugin path=file://<opencode-config-dir>/plugins/powershell-utf8-bash.js loading plugin
INFO  2026-04-27T01:43:49 +0ms service=plugin path=file://<opencode-config-dir>/plugins/opencode-beep.js loading plugin
INFO  2026-04-27T01:43:49 +0ms service=plugin path=file://<opencode-config-dir>/plugins/fixed-prompt-cache-key.js loading plugin
INFO  2026-04-27T01:43:49 +0ms service=plugin path=file://<opencode-config-dir>/plugins/codex-compaction-prompt.js loading plugin
INFO  2026-04-27T01:43:57 +1ms service=server status=completed duration=6955 method=GET path=/command request
INFO  2026-04-27T01:44:49 +52564ms service=snapshot prune=7.days cleanup

In this run, the database opened quickly, migrations ran, plugin files were loaded, and /command completed, but the second TUI still stayed on Loading plugins....

Process observation

When the second same-directory TUI is stuck, I can see two OpenCode process trees for the same project directory.

Both process trees include an opencode.exe --print-logs process and related MCP subprocesses, such as luals-mcp, serena, ast-grep-server, mcp-server-fetch, mcp-server-time, server-memory, and context7-mcp.

So the issue seems tied to starting a second TUI in the same project directory while the first one is still running.

[Hona]

does this happen in 1.14.27?
I can't repro

[Syh1906]

does this happen in 1.14.27?这个在 1.14.27 版本中是否也会出现？ I can't repro  我无法复现

I just updated to the latest version and tried again, but the second TUI CLI still fails to start properly. My environment is Windows 10, and I am not using WSL.

[Zohair-coder]

@Hona yes I can reproduce the bug in 1.14.27.

I didn't have to open two different instances of opencode to reproduce the issue. It just happens randomly each time and I can't point to what exact action is causing the issue. The best way I can reproduce it is by repeatedly launching opencode and exiting until I see the issue.

[Syh1906]

Even if I close the terminal, I still can’t get it to load when I start it again later in a project where OpenCode has already been launched. It seems like some kind of cache issue. Only a new project folder where OpenCode has never been started can launch successfully the first time — and it only works on that first launch.

[Hona]

I wonder if it has to do with using E:\ drive I recall some issues related to this.

[Zohair-coder]

Hmm my computer doesn't have an E:\ drive and I'm still seeing the issue :(

[Syh1906]

I have the same problem with my other device, I tried to start opencode in the project folder on C drive, it still fails to start

[Hona]

is anyone able to send me a full log file please?
e.g. C:\Users\Lukem\.local\share\opencode\log\ then send me the latest one?
If youre worried about private data please ping me on discord with it