fix(site/src/pages/AgentsPage): show error state with retry when chat fetch fails - #27887
Merged
Conversation
… fetch fails The chat detail and initial messages queries rendered "Chat not found" for any failure, making a transport error indistinguishable from a genuine 404. Render an error view with a retry button when either query fails without data; reserve the not-found view for a real 404 from the detail endpoint.
Contributor
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
DanielleMaywood
marked this pull request as ready for review
August 5, 2026 13:17
ibetitsmike
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Coder Agents chat page rendered "Chat not found" whenever the chat detail or initial messages query failed. A network error, 500, or timeout was indistinguishable from a genuine 404, leaving users with no way to recover short of a manual reload.
Add an error branch before the not-found branch: when either query fails with no data, the page renders a "Failed to load chat" view with a retry button that refetches both queries. The API layer (axios) throws on 404, so the not-found view is now reserved for a genuine 404 from the detail endpoint or a successful response with absent data. A background refetch that fails after content already rendered keeps showing the conversation instead of blanking the page.
Stories added to AgentChatPage: detail query error, initial messages error, retry recovery via play function, and genuine 404 still rendering "Chat not found".
PR generated by Coder Agents.