A failed chat turn shows the full wrapped error to the reader, including the provider's response body and URLs (e.g. a Gemini 429 spending-cap body). It should say what failed and what to do; the cause belongs in the gateway log.
Done when: a failed turn's live error and its stored error (shown on reopen) carry plain wording for rate limit, auth, unavailable, context length, unsupported attachment and timeout, and a generic line otherwise.
A failed chat turn shows the full wrapped error to the reader, including the provider's response body and URLs (e.g. a Gemini 429 spending-cap body). It should say what failed and what to do; the cause belongs in the gateway log.
Done when: a failed turn's live error and its stored error (shown on reopen) carry plain wording for rate limit, auth, unavailable, context length, unsupported attachment and timeout, and a generic line otherwise.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A failed chat turn shows the full wrapped error to the reader, including the provider's response body and URLs (e.g. a Gemini 429 spending-cap body). It should say what failed and what to do; the cause belongs in the gateway log.
Done when: a failed turn's live error and its stored error (shown on reopen) carry plain wording for rate limit, auth, unavailable, context length, unsupported attachment and timeout, and a generic line otherwise.
Fixed in
fe8afb18d: live and stored turn errors now carry plain wording; raw cause stays in the gateway log.