Show error state in conversation details panel when run API fetch fails#10765
Merged
Conversation
When the /api/v1/agent/runs/ API call fails to load run data, the conversation details panel now displays an error banner with a warning icon and "Failed to load run details" message instead of silently showing an empty panel. Changes: - Added is_task_fetch_failed() to AgentConversationsModel to expose whether a task fetch has failed (permanently or transiently) - Added fetch_error field to ConversationDetailsData, populated when from_task_id is called with a failed fetch state - Renders a red error banner in the panel when fetch_error is set - Updated both native (view_impl.rs) and WASM (wasm_view.rs) callers to check for fetch failure and propagate it to the details panel Co-Authored-By: Oz <oz-agent@warp.dev>
bnavetta
force-pushed
the
oz-agent/conversation-detail-panel-fetch-error
branch
from
a0f8dac to
a43644c
Compare
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR stores the failed run-fetch message in the task fetch state, emits a task update when the fetch reaches a terminal failure, and renders/copies that message in the conversation details panel for both native and WASM paths.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Instead of a generic 'Failed to load run details' message, the error banner now shows the actual error description from the server (e.g. '403 Forbidden', '500 Internal Server Error'). This is done by storing the error message string alongside the timestamp in TaskFetchState and threading it through task_fetch_error() -> from_task_id() -> the UI. Co-Authored-By: Oz <oz-agent@warp.dev>
bnavetta
force-pushed
the
oz-agent/conversation-detail-panel-fetch-error
branch
from
a43644c to
1205aab
Compare
lawsmd
pushed a commit
to lawsmd/cortex
that referenced
this pull request
May 22, 2026
…ls (warpdotdev#10765) ## Description When the `/api/v1/agent/runs/` API call fails while fetching run info for the conversation details panel, the panel now shows an error state instead of silently displaying a bare "Cloud agent run" title with no details. Instead, we should show the error message so that the user knows something went wrong and can troubleshoot or report the error. ## Testing - [x] Verified compilation with `cargo check --package warp` - [x] Verified formatting with `cargo fmt` ### Screenshots / Videos https://www.loom.com/share/e7816b6081e1445c9a694736bc33ea77 ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode CHANGELOG-BUG-FIX: The details panel for cloud agent runs now displays any failures fetching the agent metadata _Conversation: https://staging.warp.dev/conversation/b6e0e0e7-f9c7-45de-b750-20cdc029ad8e_ _Run: https://oz.staging.warp.dev/runs/019e1dc6-cd84-74b9-a544-8e704c214bd9_ _This PR was generated with [Oz](https://warp.dev/oz)._ --------- Co-authored-by: Oz <oz-agent@warp.dev>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
When the
/api/v1/agent/runs/API call fails while fetching run info for the conversation details panel, the panel now shows an error state instead of silently displaying a bare "Cloud agent run" title with no details.Instead, we should show the error message so that the user knows something went wrong and can troubleshoot or report the error.
Testing
cargo check --package warpcargo fmtScreenshots / Videos
https://www.loom.com/share/e7816b6081e1445c9a694736bc33ea77
Agent Mode
CHANGELOG-BUG-FIX: The details panel for cloud agent runs now displays any failures fetching the agent metadata
Conversation: https://staging.warp.dev/conversation/b6e0e0e7-f9c7-45de-b750-20cdc029ad8e
Run: https://oz.staging.warp.dev/runs/019e1dc6-cd84-74b9-a544-8e704c214bd9
This PR was generated with Oz.