feat(seer-explorer): show work in flight per tool call, and lead rows with the agent's own words - #122919
Open
azulus wants to merge 5 commits into
Open
feat(seer-explorer): show work in flight per tool call, and lead rows with the agent's own words#122919azulus wants to merge 5 commits into
azulus wants to merge 5 commits into
Conversation
… with the agent's own words Consumes the per-tool-call progress channel seer now emits, preferring it over `block.live_calls` and falling back where a seer does not send it. The mirror lives on the block, so with several tool calls outstanding it cannot be attributed and is shown on none of them — the reported hang. Three rendering changes alongside it. A lib record carrying an agent-written description keeps its row and hides its children: the rule's premise, that the heading says less than the rows beneath it, inverts once the heading says what the operation was for. A description leads its row, with the machine title still reachable in the expander so the claim stays checkable against what ran. And a record nothing can label is reported generically rather than deleted — an untitled record vanishing is how a whole endpoint disappears the day it is added. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Frontend
Contributor
Story previewsPreview the stories changed in this PR on the Vercel deployment: Preview deployment: https://sentry-3fdmy32f1.sentry.dev |
azulus
marked this pull request as ready for review
August 27, 2026 20:31
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 370533b. Configure here.
gricha
approved these changes
Aug 27, 2026
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A record carries `title` next to it and nothing in the old name said which was which. The generated title and the agent's own account of what it was trying to accomplish are different kinds of claim — one is derived from the call, the other is unverifiable on its own — and the rendering rules turn on exactly that distinction. Naming the field for its author makes it legible at every layer instead of only in the comments. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The fallback that gives a described row its generated title ran before the api branch, so an api call carrying a description had its request line and body preview replaced by that title. An api record's own request is the better account of what ran — it is the literal URL rather than a generated sentence — so it is built first, and the title fallback now serves only the records that ran no request of their own. Found by Cursor Bugbot on the PR. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…already say Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Consumes the per-tool-call progress channel seer emits in https://github.com/getsentry/seer/pull/7937, preferring it over
block.live_callsand falling back where a seer does not send it. The mirror lives on the block, so with several tool calls outstanding it cannot be attributed and is shown on none of them — the reported hang.Three rendering changes alongside it. A lib record carrying an agent-written description keeps its row and hides its children: the rule premise, that the heading says less than the rows beneath it, inverts once the heading says what the operation was for. A description leads its row, with the machine title still reachable in the expander so the claim stays checkable against what ran. And a record nothing can label is reported generically rather than deleted — an untitled record vanishing is how a whole endpoint disappears the day it is added.