Claude incorrectly defaults to anthropics/claude-code when creating GitHub issues

Bug Report

Claude Code incorrectly defaults to creating GitHub issues in the anthropics/claude-code repository even when working within a different repository context.

What Happened

While working on a project in repository acreeger/vfr-flight-planner, I asked Claude to create a GitHub issue for a bug. Claude created the issue in anthropics/claude-code instead of the correct repository.

Expected Behavior

Claude should:

1. Check the current git remote configuration to determine the correct repository
2. Use the repository context from the current working directory
3. Only default to anthropics/claude-code when explicitly asked or when no other repository context is available

Current Behavior

Claude defaults to anthropics/claude-code even when:

• Working in a different repository
• Git remote shows a different repository
• The entire conversation context has been about a different repository

Steps to Reproduce

1. Work on any project that isn't the claude-code repository
2. Ask Claude to create a GitHub issue
3. Observe that Claude creates the issue in anthropics/claude-code instead of the current project's repository

Technical Details

Claude should use git remote -v or similar commands to determine the correct repository owner/name before creating issues, rather than hardcoding the anthropics/claude-code repository.

Impact

• Creates issues in wrong repository
• Clutters the claude-code issue tracker with unrelated issues
• Requires manual cleanup and re-creation of issues

Example

In my case, the issue was accidentally created as https://github.com/anthropics/claude-code/issues/2128 when it should have been created in the acreeger/vfr-flight-planner repository.