The server answers failures with plain-text http.Error bodies, which the dashboard shows verbatim. Return a stable code alongside the reason (e.g. chat.composer.not_available) so the UI picks copy from ui/src/copy/errors by code, and keep server-side wording centralised like internal/prompts.
Done when internal/webui failures carry a code and the UI maps known codes to catalogue entries, falling back to the server's reason.
The server answers failures with plain-text http.Error bodies, which the dashboard shows verbatim. Return a stable code alongside the reason (e.g. chat.composer.not_available) so the UI picks copy from ui/src/copy/errors by code, and keep server-side wording centralised like internal/prompts.
Done when internal/webui failures carry a code and the UI maps known codes to catalogue entries, falling back to the server's reason.
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.
The server answers failures with plain-text http.Error bodies, which the dashboard shows verbatim. Return a stable code alongside the reason (e.g. chat.composer.not_available) so the UI picks copy from ui/src/copy/errors by code, and keep server-side wording centralised like internal/prompts.
Done when internal/webui failures carry a code and the UI maps known codes to catalogue entries, falling back to the server's reason.