[Feature Request] Feedback Status API and Consolidated Tracking System

Bug Description
Feature Request: Feedback Status API and Consolidated Tracking

From: Jordan Dea-Mattson
GitHub: @jordan-of (OrdinaryFolk), @jordandm (personal)
Email: jordan-of@users.noreply.github.com

Problem

Feedback submitted via /feedback and GitHub issues enters a black box. There is no way to:

• Check the status of a submission after filing it
• Know whether it was read, consolidated with similar reports, accepted, rejected, or scheduled
• See how many other users reported the same thing
• Know if a fix or feature is in progress

The current GitHub workflow compounds this: a bot auto-closes issues as "duplicates" based on text similarity, with no human verification. All four of my closed issues were bot-closed this way.
The linked "duplicate" issues may or may not actually describe the same problem — but I have no way to verify, no notification when the canonical issue progresses, and no indication that my
specific report was actually read by a human. The message to the reporter is: your feedback disappeared.

Meanwhile, Anthropic asks users to "upvote" duplicate GitHub issues manually. This puts the burden on the reporter to find duplicates, navigate to them, and react — work that the system should
handle automatically.

Requested Behavior

1. Feedback Status API

A way to check the status of submitted feedback, accessible via:

• /feedback status — list my recent submissions and their current state
• /feedback status <id> — check a specific submission
• A web dashboard (optional, nice to have)

Status lifecycle:

submitted → acknowledged → triaging → consolidated → [accepted | rejected | deferred]
↓
scheduled → in-progress → shipped

Each status should include:

• Current state and when it changed
• Canonical tracker ID — if consolidated with similar reports, link to the canonical item
• Similar report count — "12 other users reported this" gives confidence it's being noticed
• Resolution notes — if rejected or deferred, a brief explanation why

1. Automatic Consolidation (Replace Auto-Close)

When a new submission matches an existing tracked item:

• Don't close the issue. Link it to the canonical tracker instead.
• Notify the reporter: "Your report has been linked to [canonical item]. You'll be notified when it progresses."
• Auto-upvote the canonical item on the reporter's behalf — don't ask them to do it manually
• Preserve the reporter's original text as a data point (different users describe the same problem differently, and that's valuable signal)

This replaces the current bot behavior which:

• Auto-closes as "duplicate" with no human review
• Links to "possible" duplicates that may not be the same issue
• Locks the issue after 7 days, preventing the reporter from disputing the match
• Loses the reporter's specific context and framing

1. GitHub Integration

• When a /feedback submission also creates a GitHub issue, link them bidirectionally
• Status updates from the internal tracker should reflect on the GitHub issue (comment or label)
• When the canonical item ships, auto-close all linked GitHub issues with a "shipped in version X" comment
• Upvotes from consolidated reports should be reflected as reactions on the canonical GitHub issue

Why This Matters

Feedback is a contract between the reporter and the product team. The reporter invests time describing a problem; the implicit promise is that someone will read it and act on it. When submissions
vanish into a black box — or worse, get auto-closed by a bot — that contract breaks. Reporters stop filing feedback, and the product team loses signal.

A status API and consolidation system closes the loop:

• For reporters: visibility into whether their feedback matters
• For Anthropic: structured signal on what users care about most (ranked by report count, not just GitHub reactions)
• For the product: a pipeline from feedback → triage → feature → shipped, with reporters notified at each stage

The auto-close-as-duplicate pattern is particularly damaging for power users who file multiple reports. Being told "this is a duplicate" by a bot, with no human verification and a 7-day lock, is a
signal that detailed feedback isn't valued. The consolidation model inverts this: "thanks, 12 others agree, here's where we're tracking it" tells the reporter their voice was heard.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.80
• Feedback ID: 8f11a3f9-3392-4a27-8369-a92d18caf362

Errors

[{"error":"Err…

Note: Content was truncated.