Claude Code defaults to `anthropics/claude-code` repo instead of current project when referencing GitHub issues

Resolved 💬 4 comments Opened Nov 27, 2025 by monneyboi Closed Jan 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description:

When I ask Claude Code to look at a GitHub issue by number (e.g., "Let's tackle GitHub issue 77"), it defaults to querying the anthropics/claude-code repository instead of my current project's repository.

Expected behavior:

Claude Code should default to the repository of the current working directory, matching how gh issue view <number> works when run without a --repo flag.

Actual behavior:

Claude Code first attempts to query anthropics/claude-code, likely because it associates itself with Anthropic. This requires me to correct it before it checks my actual project.

What Should Happen?

When a user references a GitHub issue without specifying a repository, always default to the current project's repo (detectable via git remote or the gh CLI's default behavior).

Error Messages/Logs

Steps to Reproduce

Ask Claude Code to look at a GitHub issue by number (e.g., "Let's tackle GitHub issue 77")

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.55 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

This seems to have started happening with latest Opus 4.5. When I was mostly using Sonnet 4.5 and Opus 4.1, I never had this problem.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗