[Bug] Unhandled crash in `Provider.list` when Cloudflare environment variables exist without `CLOUDFLARE_API_TOKEN`

[mindofcharles]

Description

Description

When launching OpenCode (opencode), the TUI interface fails to start and immediately crashes with the following generic error:

Error: Unexpected server error. Check server logs for details.
    at <anonymous> (/$bunfs/root/chunk-3mfps532.js:8:7615)
    at processTicksAndRejections (native:7:39)

No relevant logs are written to ~/.local/share/opencode/log/, making troubleshooting difficult in default mode.

Root Cause

Running the server directly via opencode serve --print-logs --log-level DEBUG --pure exposed the underlying unhandled exception:

Error: CLOUDFLARE_API_TOKEN (or CF_AIG_TOKEN) is required for Cloudflare AI Gateway. Set it via environment variable or run `opencode auth cloudflare-ai-gateway`.
    at <anonymous> (/$bunfs/root/chunk-dfdqwmkx.js:439:73202)
    at Provider.list (/$bunfs/root/chunk-wrjsh8a1.js:4:1338)
    at Provider.list (definition) (/$bunfs/root/chunk-dfdqwmkx.js:439:87629)
    at ProviderHttpApi.list (/$bunfs/root/chunk-wrjsh8a1.js:2:84381)
    at ProviderHttpApi.list (definition) (/$bunfs/root/chunk-wrjsh8a1.js:4:1057)
    at Server.listen (/$bunfs/root/chunk-wrjsh8a1.js:6:15456)
    at Server.listen (definition) (/$bunfs/root/chunk-wrjsh8a1.js:6:15579)

• Trigger: OpenCode automatically parses system environment variables (e.g., CLOUDFLARE_ACCOUNT_ID in ~/.zshrc).
• Bug: During Provider.list initialization, if a partial Cloudflare configuration is detected without a corresponding CLOUDFLARE_API_TOKEN (or CF_AIG_TOKEN), the backend throws an unhandled fatal error instead of skipping or gracefully disabling the provider. This completely breaks the local server and prevents OpenCode from starting.

Expected Behavior

1. Graceful Fallback: If required credentials for a provider are missing, OpenCode should ignore, skip, or mark that specific provider as inactive rather than terminating the entire server process.
2. Proper Error Logging: Fatal startup errors should be properly captured and written to the log directory so users can diagnose the failure without running internal headless debugging flags.

---

I believe OpenCode should not automatically read or infer system environment variables without the user's explicit consent or specification.

---

Issue #33780 was also caused by this problem.

Plugins

NO

OpenCode version

1.18.18

Steps to reproduce

1. Set a partial Cloudflare environment variable in your shell profile (e.g., export CLOUDFLARE_ACCOUNT_ID="your_account_id") without setting CLOUDFLARE_API_TOKEN.
2. Run opencode in the terminal.
3. Observe the startup crash with Unexpected server error.

Screenshot and/or share link

NO

Operating System

macOS 26.6.1 (Darwin arm64)

Terminal

macOS Terminal

[github-actions]

This issue might be a duplicate of or closely related to existing issues. Please check:

• Unexpected server error on startup (macOS 26) #33780: Same "Unexpected server error" crash on startup (macOS), by the same author — the current issue appears to be the root cause investigation of that earlier report. Consider whether this should be linked as a follow-up or the older issue closed in favour of this one.
• [Bug] Desktop v1.17.14 Provider.list() TypeError crash - UI shows no models/providers on every startup #35772: Provider.list() crash on startup causing empty model/provider list — different root cause (undefined property read vs. missing Cloudflare token) but the same crash site and symptom pattern.

If this issue supersedes #33780, it may be worth closing that one and referencing this issue instead.

[mindofcharles]

Additional Context: Scope of the Issue

Looking closely at the stack trace (Provider.list), this appears to be a general issue in how OpenCode discovers and initializes built-in providers rather than being strictly specific to Cloudflare.

If the initialization loop in Provider.list evaluates environment variables for every built-in provider on startup, any provider that throws a validation error on partial/missing credentials will take down the entire server process.

[MilkyWay008]

Saw the same Error: Unexpected server error in the wild, and the debug serve flags you found are exactly the right way to surface it. That one's the provider env-scan: CLOUDFLARE_ACCOUNT_ID was set without CLOUDFLARE_API_TOKEN, so Provider.list throws before the TUI even boots. Quick unblock is env -u CLOUDFLARE_ACCOUNT_ID opencode or unsetting the partial Cloudflare vars in ~/.zshrc, and worth peeking at #33780/#35772 in case the env-scan fix already landed past 1.18.18.

[mindofcharles]

Yeah, I actually opened #33780 too—it was the exact same issue (which is why I closed it). Also, the PR addressing #35772 wasn't merged and got closed.