OpenCode don't start after the migration

[NazmiAltun]

Description

I was one of the older versions ( last used 2 weeks ago). Yesterday, i run opencode and i migrated to the latest version (i guess it also did some db migration) and after that db migration it stopped working. When i run opencode in my terminal it opens up a black screen and got stuck there.

Plugins

"@franlol/opencode-md-table-formatter@latest",
"opencode-websearch-cited@latest",
"opencode-pty",
"opencode-openai-codex-auth",
"yet-another-opencode-cursor-auth"

OpenCode version

1.2.10

Steps to reproduce

1. type opencode in terminal and hit enter

Screenshot and/or share link

Screen.Recording.2026-02-22.at.11.09.17.mov

Operating System

macOS 26.3

Terminal

Ghostty

[github-actions]

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

• Updating to 1.2.x hangs on sql migration #14264: Updating to 1.2.x hangs on sql migration (same symptom: stuck/black screen after db migration on upgrade)
• Black screen on startup after upgrading to version 1.2.7 #14336: Black screen on startup after upgrading to version 1.2.7 (same symptom: black screen after version upgrade)
• black screen only on desktop App. working well on TUI #14338: Black screen only on desktop app (similar black screen symptom after update)

If your issue is the same, please add a thumbs-up reaction or comment on the existing issue rather than opening a new one. If your issue is different, please clarify what distinguishes it.

[Anonmike]

same, Ubuntu 25.04 x86_64, default terminal, it just started last night but already opened opencode instances on tmux still work, just can't start a new one
v1.2.10 tried downgrading to v1.2.9 same thing

[ominiverdi]

Root cause (relates to #14336, #14338, #14636, possibly #14264)

The black/white screen on startup (TUI and Desktop) is caused by opencode's embedded bun runtime hanging indefinitely while resolving packages from the npm registry.

On every launch, opencode runs:

1. opencode install in ~/.config/opencode/ and ~/.opencode/ -- bun hangs resolving @opencode-ai/plugin
2. opencode add --force for each plugin in the config array
3. opencode add --force for each BUILTIN plugin hardcoded in the binary

All three use bun internally. Bun hangs at "Resolving dependencies" for @opencode-ai/plugin. The same packages install fine with npm in ~3 seconds. Reproducible on bun v1.3.5 and v1.3.10 on Linux x86_64.

The binary also has a hardcoded BUILTIN = ["opencode-anthropic-auth@0.0.13"] list that gets prepended to the user's plugin array on every startup. Despite the name, these BUILTIN entries are not embedded in the binary -- they are downloaded from npm via BunProc.install(). The upstream repo (anomalyco/opencode-anthropic-auth) has been deleted and the npm package is deprecated, yet the binary still tries to fetch it. This means even users with no plugins in their config are affected by the bun hang. Setting OPENCODE_DISABLE_DEFAULT_PLUGINS=1 skips the BUILTIN list but requires manually configuring auth plugins.

Related issues:

• Black screen on startup after upgrading to version 1.2.7 #14336 -- Black screen on Desktop after upgrading to v1.2.7
• black screen only on desktop App. working well on TUI #14338 -- Black screen on Desktop, TUI works
• OpenCode don't start after the migration #14636 -- Black screen after DB migration
• Updating to 1.2.x hangs on sql migration #14264 -- Updating to 1.2.x hangs on SQL migration (possibly same cause)

Workaround

This is a temporary workaround until opencode fixes the startup resolution. Fully reversible.

Step 1 -- Pre-install with npm and create a bun.lock so bun skips resolution:

cd ~/.config/opencode && rm -rf node_modules bun.lock package-lock.json && npm install
cd ~/.opencode && rm -rf node_modules bun.lock package-lock.json && npm install

Then generate a bun.lock from the npm lockfile in ~/.config/opencode/ (see script below) so that opencode's embedded bun sees a matching lockfile and skips network resolution.

Step 2 -- If you have plugins in the "plugin" config array, reference them as local paths instead of npm packages to avoid bun add --force:

# Install the plugin once with npm
mkdir -p ~/.cache/opencode
echo '{"dependencies":{"your-plugin-name":"x.y.z"}}' > ~/.cache/opencode/package.json
cd ~/.cache/opencode && npm install

Then in ~/.config/opencode/opencode.json:

- "plugin": ["your-plugin-name@x.y.z"]
+ "plugin": ["/home/USER/.cache/opencode/node_modules/your-plugin-name/index.mjs"]

bun.lock generation script (Python 3)

Run this in ~/.config/opencode/ after npm install:

import json
with open('package-lock.json') as f:
    lock = json.load(f)
with open('package.json') as f:
    pkg = json.load(f)
lines = ['{', '  "lockfileVersion": 1,', '  "configVersion": 1,',
         '  "workspaces": {', '    "": {', '      "dependencies": {']
for name, ver in pkg.get('dependencies', {}).items():
    lines.append(f'        "{name}": "{ver}",')
lines.extend(['      },', '    },', '  },', '  "packages": {'])
for path, info in lock.get('packages', {}).items():
    if not path or not path.startswith('node_modules/'): continue
    name = path.replace('node_modules/', '')
    v, integrity = info.get('version',''), info.get('integrity','')
    meta = {}
    if info.get('dependencies'): meta['dependencies'] = info['dependencies']
    if info.get('optionalDependencies'): meta['optionalDependencies'] = info['optionalDependencies']
    if info.get('os'): meta['os'] = info['os'][0] if len(info['os'])==1 else info['os']
    if info.get('bin'): meta['bin'] = info['bin']
    entry = f'    "{name}": ["{name}@{v}", "", {json.dumps(meta)}'
    if integrity: entry += f', "{integrity}"'
    lines.append(entry + '],')
lines.extend(['  }', '}'])
with open('bun.lock', 'w') as f:
    f.write('\n'.join(lines))
print('bun.lock generated')

Expected fix from opencode

This workaround should become unnecessary once opencode addresses the startup resolution. Possible fixes:

• Skip network resolution when node_modules/ already satisfies package.json
• Add a timeout with fallback to cached modules -- the UI should never be blocked by a package manager
• Don't resolve BUILTIN plugins from npm -- opencode-anthropic-auth is not embedded in the binary despite being in the BUILTIN list; the upstream repo is deleted and the npm package deprecated, yet BunProc.install() still tries to fetch it on every launch

How to revert (once fixed upstream)

1. Delete the generated bun.lock files (or let opencode overwrite them)
2. Change local plugin paths back to npm references in opencode.json
3. The npm-preinstalled node_modules/ won't cause any conflict

Environment

• opencode TUI v1.2.14/v1.2.15, Desktop v1.2.15
• Linux x86_64 (also reported on macOS and Windows in Black screen on startup after upgrading to version 1.2.7 #14336, black screen only on desktop App. working well on TUI #14338)
• bun v1.3.5 and v1.3.10 both affected (opencode uses its own embedded bun)

[ominiverdi]

Additional possibly related issues

After further investigation, this bun resolution hang on startup might affect more reported issues beyond the ones cited above. Any issue where the UI shows a black/white/blank screen while bun processes are running in the background could share the same root cause.

Possibly direct match (v1.2.7+ and the deprecated opencode-anthropic-auth BUILTIN):

• Black screen #14334, Black screen Linux App #14335, Black screen on startup after upgrading to version 1.2.7 #14336, black screen only on desktop App. working well on TUI #14338 -- all opened Feb 19 (the day the anthropic-auth plugin was deprecated)
• The OpenCode desktop version displays a blank screen #15185 -- still reported today (Feb 26) on v1.2.15

Same pattern with other plugins (bun hangs on add --force):

• White screen on startup when opencode-gemini-auth plugin is enabled #14620 -- white screen with opencode-gemini-auth plugin
• Black Screen after install Oh-my-opencode Plugin #12192 -- black screen after installing oh-my-opencode
• Windows 11: GUI opens but stays blank, no logs, bun processes running #12491 -- Windows blank screen, bun processes running
• Startup shows blank screen for several seconds when plugins are configured #12666 -- blank screen when plugins are configured
• Plugin syntax/build errors cause black screen with no user-facing error message #13461 -- plugin errors cause black screen with no error message

Startup lag likely caused by slow bun resolution:

• Significant startup lag (blank screen) in Ubuntu #14167 -- significant startup lag (blank screen) in Ubuntu
• Slow startup #14965 -- slow startup since v1.2.1

These may have different root causes (hardware acceleration, Rosetta 2, etc.), but the bun resolution hang could explain the symptom in many of them.

[viethung26]

I am experiencing the exact same black screen issue after reinstalling OpenCode on WSL2. It worked fine initially, but after an uninstallation and reinstallation, the UI stays black and won't load.

Environment:
OS: Windows 11 (WSL2 - Ubuntu)
Node version: v24.11.1
OpenCode version: 1.2.24