Repository navigation
[BUG] gitStatus in the system reminder gets stale #3901
Description
Environment
- Platform (select one):
- Anthropic API
- AWS Bedrock
- Google Vertex AI
- Other:
- Claude CLI version: 1.0.55 (Claude Code)
- Operating System: Ubuntu 24.04
- Terminal: VSCode over ssh
Bug Description
The system reminder apparently keeps a gitStatus piece of info that goes stale
Steps to Reproduce
- Work with Claude Code a bunch doing git operations.
- Ask Claude to cleanup old feature branches that were merged on origin and switch back to the main branch.
- Issue a /clear when ready.
- Ask Claude "what's next?" and he casually mentions a feature branch that isn't the current git branch, doesn't even exist anymore, and Claude is the one who got rid of it.
Expected Behavior
Claude doesn't have any stale info after a /clear, let alone after operations Claude undertook directly.
Actual Behavior
Claude said "Looking at your current branch feature/deployment-improvements and the modified files, it appears you've been working on infrastructure deployment improvements. Let me check what specific tasks or issues might be next." Our current branch was main and no other branches exist locally.
Activity
ohmantics commentedon Jul 18, 2025
Claude suggested him issuing a git status and that didn't clear it. Using /exit and restarting Claude finally reset gitStatus to be accurate.
benreynwar commentedon Jul 30, 2025
I observed the same issue that /clear didn't refresh gitStatus. /exit also worked for me.
github-actions commentedon Aug 16, 2025
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Aug 20, 2025
This issue has been automatically closed as a duplicate of #2538.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Aug 28, 2025
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.