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
Plugin installer silently fails for git-based specs (github:, git+https://) #48473
Git-based plugin specs in tui.json fail silently on TUI startup. The cache directory is created but stays empty (no package.json / package-lock.json / node_modules), the plugin never loads, and nothing is logged — even with OPENCODE_LOG_LEVEL=0. No error in the TUI either.
Registry specs (pkg@latest) and file:// path specs work fine in the same environment, so it's specific to git specs. The same git spec installs fine with stock tooling: npm install "github:owner/repo#<sha>" succeeds, and node + @npmcli/arboristreify({ add: [spec] }) succeeds.
The github: shorthand resolves to ssh://[email protected]/... (no SSH keys configured here), but an explicit git+https:// spec fails the same way, so it's not just the ssh transport.
Add to ~/.config/opencode/tui.json: { "plugin": ["github:skolkin-worker/opencode-sessions-sidebar#2dce6f3..."] }
Restart the TUI
~/.cache/opencode/packages/<spec>/ is created but empty; plugin not loaded; no install/load/failure entries in ~/.local/share/opencode/log/opencode.log even with OPENCODE_LOG_LEVEL=0
Same outcome with the git+https:// variant.
Screenshot and/or share link
— (no error UI to screenshot; the only artifact is the empty cache dir)
Activity
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊