[FEATURE] Let users view/track the feedback they've submitted

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Feedback submitted via /feedback disappears into Anthropic's systems with no user-facing record. There is no way to see what has already been reported, whether a new observation duplicates a prior one, or whether a past report was ever addressed.

Public issue trackers make open-source contribution legible by design: a contributor's history is visible, citable, and buildable-on by others. Feedback submitted through Claude Code currently has none of that property — it is a one-way channel with no record of a user's own contribution over time.

Proposed Solution

Expose a simple, local or account-level log of feedback the user has submitted: title, timestamp, and status if triaged. Even a minimal /feedback --history listing, or a local receipt file written at submission time, would substantially improve this.

Alternative Solutions

None currently exist. A user can keep their own copy of what they submitted only by manually saving the text before sending, which is easy to forget and produces no linkage back to Anthropic's own tracking (e.g., a feedback ID, triage status).

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

1. I work with Claude Code 15-20 hours a day and file feedback regularly.
2. Weeks later, I notice a related issue and want to check whether I already reported the underlying cause, or only a symptom of it.
3. There is currently no way to answer that question without having kept my own external notes.
4. A local history view would let me check instantly, and would give a heavy contributor the same sense of legible, cumulative contribution that a public issue tracker gives an open-source contributor.

Additional Context

Companion issue, filed alongside this one: #92519 (granular control over conversation context attached to feedback). Both stem from the same underlying gap — the feedback channel currently treats every submission as fire-and-forget, whether the question is "what did I send" (this issue) or "how much of my session did I send" (the companion issue).