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
Server error responses carry stack traces; an unavailable remote config makes every request a 500 #1787
When altimate-code serve hits an error it doesn't recognise, the HTTP response body carries the error's full stack trace: runtime frames and internal file paths. Clients such as the VS Code extension then show or record it.
The most common trigger is a wellknown auth entry whose remote config (<url>/.well-known/opencode) answers with an error or refuses the connection. Config loading turns that into an untyped error. So every request, including GET /agent (the agent list the chat panel asks for), answers HTTP 500 with the stack, and nothing says which service failed or why.
Expected:
An unavailable remote config is reported as such: which remote, and its HTTP status or the connection failure, with HTTP 502.
No response carries a stack trace or an error's internal text. The server logs it instead, under a reference that the response carries. The /api routes already answer this way.
Plugins
None
OpenCode version
main (an unknown route shows the same 500 body on v0.12.11)
Steps to reproduce
Add a wellknown entry to auth.json whose URL answers HTTP 500 to /.well-known/opencode, or points at a closed port.
Run altimate-code serve.
Request GET /agent. It answers HTTP 500 with a body like {"name":"UnknownError","data":{"message":"Error: failed to fetch remote config from …/.well-known/opencode: HttpClientError: StatusCode: non 2xx status code (500 …)\n at <anonymous> (…/src/config/config.ts:341:50)\n at …/node_modules/…/effect/…"}}.
Separately, without any remote config, any route the server doesn't know answers HTTP 500 with the same kind of body.
Activity
sahrizvi commentedon Nov 21, 2026
Resolved in v0.12.12.