Claude Code should proactively detect user pain points and auto-submit or upvote GitHub issues

Suggested by: @Orionsg

Summary

Claude Code should proactively detect when a user expresses a pain point, workflow gap, or feature suggestion during a conversation, search existing open issues for the same topic, and either upvote/comment on an existing issue or create a new one — all without the user needing to leave the conversation or navigate GitHub manually.

Motivation

Users naturally articulate frustrations and ideas in the flow of conversation. These observations are valuable feedback, but most users never file them because it requires context-switching to GitHub, reformulating the problem from scratch, and knowing which repo to target.

Claude already has the full context of what the user experienced and what they want. It is better placed than the user to write a clear, well-structured issue at that moment — and to avoid creating duplicate noise by checking what already exists.

Proposed Behaviour

1. During a conversation, Claude detects when the user voices a pain point or suggestion about Claude Code itself.
2. Claude proactively offers: "This sounds like a feature gap — want me to check the Claude Code repo and file or upvote an issue for it?"
3. If the user agrees, Claude searches existing open issues for the same topic and takes one of three actions:

• Exact match found → reacts with 👍 on the existing issue and returns the link
• Partial match found → reacts with 👍 and adds a comment covering the aspects not already described, noting what was added
• No match found → drafts and creates a new, well-structured issue

1. Claude confirms the outcome with a direct link to the issue.

Token Usage

Token consumption for detecting, drafting, searching, and submitting such issues should not be billed to the user. This activity is meta-work that benefits Anthropic's own feedback loop, not the user's primary task.

Scope

• Limited to Claude Code itself (anthropics/claude-code) — not user projects or third-party repos.
• Should not fire on vague complaints; only on clearly actionable, specific observations.

Example

User: "It's strange that the desktop app always defaults to the last session's folder — there's no folder picker." Claude: "That's a known gap. Want me to check the Claude Code repo and file or upvote an issue for it?" User: "Yes." Claude: (searches issues → finds partial match #36175 → upvotes and adds comment covering the missing aspect → returns link)