[FEATURE] Let Claude search existing GitHub issues (read-only, public repos) to prevent duplicate reports

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

When a user asks Claude (claude.ai, cloud session) to help report a bug to anthropics/claude-code, Claude cannot reliably check whether the issue already exists, so duplicates reach the team.

What Claude ran into in such a session:

• gh search issues → 403: GitHub GraphQL is not available from Claude Code sessions.
• REST search/issues → 403: "sessions are bound to their configured repositories".
• REST repos/anthropics/claude-code/issues → 403: access not enabled, use add_repo.
• add_repo anthropics/claude-code → fails until the user links a GitHub account, even for read access to a public repo.
• WebFetch of github.com/.../issues?q=... → blocked by GitHub's robots.txt.

Only a general web search engine works, and it covers only issues that happen to be indexed. It did find a closely related issue (#41653) that the API route could not.

Result: the user must search manually, or files without checking, which increases duplicate triage load.

Proposed Solution

Give cloud sessions read-only access to GitHub issue search for public repositories, without requiring the user to link a GitHub account, at least for anthropics/* repos. For example, allow the REST search/issues endpoint (and repos/{owner}/{repo}/issues GET) through the agent proxy for public repos.

Ideally, when a session drafts a report for anthropics/claude-code, Claude searches for duplicates first and links candidates in its draft.

Alternative Solutions

• Make add_repo with read access work on public repos without a linked GitHub account.
• Provide a dedicated tool/MCP for searching Anthropic's public issue trackers.
• Status quo: rely on web search, which is incomplete.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

1. My plugin marketplace passed claude plugin validate but failed to sync on claude.ai.
2. I diagnosed it with Claude in claude.ai, which drafted a bug report for this repo.
3. Claude could not check for existing reports via GitHub's API and told me so; I had to search myself before ticking "I have searched existing issues".
4. With read-only issue search, Claude would have checked for duplicates and linked related issues (e.g. #41653) in the draft.

Additional Context

The 403 messages come from the session's GitHub proxy (they point to docs.anthropic.com/en/docs/claude-code/github-actions), so this is a configuration of Claude's cloud sessions rather than a GitHub limitation.