Repository navigation
OPENCODE_SERVER_PASSWORD breaks TUI startup with --mdns or --hostname #29847
Description
Setting OPENCODE_SERVER_PASSWORD breaks normal TUI startup when using --mdns or --hostname.
Repro
export OPENCODE_SERVER_PASSWORD=changeme123
opencode --mdnsAlso fails with:
export OPENCODE_SERVER_PASSWORD=changeme123
opencode --hostname 0.0.0.0Error
Error: 4 of 6 requests failed:
config.providers: opencode server GET http://0.0.0.0:4096/config/providers?... → 401 Unauthorized
provider.list: opencode server GET http://0.0.0.0:4096/provider?... → 401 Unauthorized
app.agents: opencode server GET http://0.0.0.0:4096/agent?... → 401 Unauthorized
config.get: opencode server GET http://0.0.0.0:4096/config?... → 401 UnauthorizedExpected
TUI should start successfully.
If OPENCODE_SERVER_PASSWORD enables Basic auth, internal TUI requests should include auth or otherwise work.
Why it matters
--mdns and --hostname 0.0.0.0 expose OpenCode on LAN. Password auth should be usable with those modes.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 29, 2026
This issue might be a duplicate of existing issues. Please check:
OPENCODE_SERVER_PASSWORDcauses the internal client to receive 401 Unauthorized from its own in-process server. That issue coversopencode run; this one covers the TUI with--mdns/--hostname, but the underlying problem appears to be the same.OpeOginni commentedon May 29, 2026
I am able to reproduce, and I am looking at a fix!