anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Opencode should fall back to cached well-known config when endpoint is temporarily unavailable #7795

New Issue
Open
opened 2026-02-16 18:08:15 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:08:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @MaxMiksa on GitHub (Jan 28, 2026).

Originally assigned to: @thdxr on GitHub.

Description

If a user has a wellknown credential configured, Config.get() fetches <url>/.well-known/opencode during startup. If that endpoint is temporarily unavailable (e.g. 500, network hiccup, timeout), Opencode fails to start because config loading hard-throws.

This makes org/enterprise setups brittle: a transient config outage bricks the CLI/agent even if local/project config could still be used.

Suggested fix

  • Cache the last successful well-known config payload locally (e.g. XDG cache).
  • On fetch failure, fall back to the cached config (with a warning) instead of hard-failing.
  • Add a configurable fetch timeout (e.g. OPENCODE_WELLKNOWN_TIMEOUT_MS).

Steps to reproduce

  1. Configure a well-known credential (e.g. via opencode auth login <url>).
  2. Ensure <url>/.well-known/opencode becomes unavailable (500 / offline) after a successful run.
  3. Start Opencode again.

Expected

Opencode starts and uses the cached well-known config (and logs a warning).

Actual

Opencode throws failed to fetch remote config from <url>: <status> during config load and exits.

Environment

  • OS: Windows 11 (also affects any OS on transient network failures)
  • Terminal: Windows Terminal
Originally created by @MaxMiksa on GitHub (Jan 28, 2026). Originally assigned to: @thdxr on GitHub. ### Description If a user has a `wellknown` credential configured, `Config.get()` fetches `<url>/.well-known/opencode` during startup. If that endpoint is temporarily unavailable (e.g. 500, network hiccup, timeout), Opencode fails to start because config loading hard-throws. This makes org/enterprise setups brittle: a transient config outage bricks the CLI/agent even if local/project config could still be used. ### Suggested fix - Cache the last successful well-known `config` payload locally (e.g. XDG cache). - On fetch failure, fall back to the cached config (with a warning) instead of hard-failing. - Add a configurable fetch timeout (e.g. `OPENCODE_WELLKNOWN_TIMEOUT_MS`). ### Steps to reproduce 1. Configure a well-known credential (e.g. via `opencode auth login <url>`). 2. Ensure `<url>/.well-known/opencode` becomes unavailable (500 / offline) after a successful run. 3. Start Opencode again. ### Expected Opencode starts and uses the cached well-known config (and logs a warning). ### Actual Opencode throws `failed to fetch remote config from <url>: <status>` during config load and exits. ### Environment - OS: Windows 11 (also affects any OS on transient network failures) - Terminal: Windows Terminal
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7795
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?