Skip to content

feat(feedback): Prototype agent feedback views - #131737

Draft
scttcper wants to merge 1 commit into
masterfrom
scttcper/agent-feedback-prototype
Draft

scttcper wants to merge 1 commit into
masterfrom
scttcper/agent-feedback-prototype

Conversation

@scttcper

Copy link
Copy Markdown
Member

Experiment only, not intended to be merged. Opening as a draft to share the idea.

The feedback page is built around people using the widget, but feedback on an MCP server mostly comes from agents that got stuck. For those the trace preview is always empty since every tool call is its own trace, and the structure agents send (task, tool, impact) is buried in the tags.

For agent reports this swaps the trace preview for an Agent Session section that lists the tool calls that user made before the report, with the arguments, what the tool returned and the logs for each call. The failed call the report is about opens by default. A Tool Health section shows the reported tool's call volume and failure rate, and the list gets a reports-by-tool table with impact filters.

Not behind a flag and no tests. Agent reports are detected by reporter name in the list because the issue doesn't carry the feedback source.

Experiment, not meant to merge. The feedback page is built around people
using the widget, but an MCP server's feedback is mostly agents that got
stuck, and for those the trace preview is always empty because every
tool call is its own trace.

Agent reports get an Agent Session section instead: the tool calls that
user made before the report, pulled from mcp.server spans, with the
arguments, what the tool returned and the logs on each call. The failed
call the report is about opens by default. Tool Health puts the reported
tool's call volume and failure rate next to it.

The list gets a reports-by-tool table with call counts and failure
rates, impact filters, and rows titled by the task instead of the
reporter name.

Not behind a flag. Agent reports are detected by reporter name in the
list since the issue doesn't carry the feedback source.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

Metric Before After Delta
Coverage 96.08% 96.08% ±0%
Typed 144,031 144,255 🟢 +224
Untyped 5,878 5,883 🔴 +5
🔍 5 new type safety issues introduced

any-typed symbols (1 new)

File Line Detail
static/app/components/feedback/agent/useAgentSession.tsx 231 parsed (var)

Non-null assertions (!) (4 new)

File Line Detail
static/app/components/feedback/agent/agentFeedback.ts 52 lines[index]!
static/app/components/feedback/agent/agentFeedback.ts 56 lines[index]!
static/app/components/feedback/agent/agentSessionSection.tsx 214 toolCalls[0]!
static/app/components/feedback/agent/useAgentToolStats.tsx 109 tagValue.value!

This is informational only and does not block the PR.

This branch was successfully deployed

1 active deployment
Preview — d7dd7ec8 Deployed Nov 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant