OpenCode API key expiry leaves VS Code plugin users without config docs
VacantFuture · ghdev · 2026-10-18
A user hit a litellm.AuthenticationError (apikeyexpired) in opencode 1.19.3 (VS Code plugin on Pop!OS) while using the remote qwen3.5-plus model via ZEN. Previously no API key was needed for remote models; after creating a new key in OpenCode Console per the error message, they found documentation only covers setting the key as an auth bearer token in curl — nothing on configuring it in the VS Code plugin or CLI, and signing in again doesn't renew the key.
The issue (labels: pending close, triaging; 4 comments) highlights a gap in opencode's key rotation flow and client-side configuration docs.
More from coding & agent
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- Capy 0.5.0 lets Claude Pro/Max subscribers reuse their plan quota, adds OIDC cloud access — garrytan · 2026-10-23
- You.com CEO Richard Socher: legacy code is human slop, let AI clean it up — RichardSocher · 2026-10-23
- Let agents design a single-line glance component so you can track them from the sidebar — blixt · 2026-10-23