You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CRITICAL: Claude Code regression — model now consistently fails basic tasks and hallucinates in code analysis #33908
Claude Code (claude-opus-4-6) failed to locate the global MCP configuration file at /Users/mehparmar/.claude.json during a straightforward user query: "where are MCPs configured globally?"
What happened
Instead of directly checking the obvious location (/Users/mehparmar/.claude.json), the model:
Ran multiple broad find ~/ searches across the entire home directory
Dug into plugin cache directories unnecessarily
Read plugin registry files looking for MCP server definitions
Eventually found .mcp.json inside a plugin cache subdirectory but still failed to check the root user config location
Required the user to explicitly point out the file at /Users/mehparmar/.claude.json
Expected behavior
A simple, direct lookup:
ls -la /Users/mehparmar/.claude.json
# or
cat ~/.claude.json
This file location failure is part of a larger pattern of performance degradation across multiple domains:
1. Basic Question Answering
Claude struggles with straightforward questions that should be trivial
Requires multiple clarifications and round-trips for simple context understanding
Poor ability to infer intent from context
2. Bug Diagnosis & Code Analysis (CRITICAL)
Java/Go Polyglot Codebase Example:
Claude (2+ days of effort): Unable to identify root cause, hallucinated about wrong code sections, focused on unrelated components, missed obvious patterns
Codex with GPT 5.4 (15 minutes): Immediately identified root cause, provided clear diagnosis and fix
3. Code Search & Navigation
Inefficient file location (this issue)
Required explicit user guidance to find obvious files
Multiple rounds to locate standard config files
4. Pattern Recognition in Large Codebases
Hallucinating code patterns that don't exist
Missing actual patterns in favor of speculative wrong answers
Unable to correlate related code sections across files
Key Metrics
Regression Timeline: Last 3 days (measurable decline)
Accuracy Impact: Not marginal — fundamental degradation in core capabilities
Severity: CRITICAL for developers relying on Claude for real code maintenance and debugging
Why this matters
This is not just about file location performance. The root issue is accuracy and reasoning quality fundamentally degrading on tasks Claude was previously excellent at. For a tool designed to help with code understanding and debugging, this regression makes it unreliable for critical development work.
changed the title [-]Performance regression: Claude Code unable to locate simple config files like .mcp.json[/-][+]CRITICAL: Claude Code regression — model now consistently fails basic tasks and hallucinates in code analysis[/+]on Mar 13, 2026
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.
Activity
github-actions commentedon Mar 13, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
[-]Performance regression: Claude Code unable to locate simple config files like .mcp.json[/-][+]CRITICAL: Claude Code regression — model now consistently fails basic tasks and hallucinates in code analysis[/+]github-actions commentedon Apr 10, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Apr 18, 2026
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.