[BUG] Claude Code repeatedly loses cross-session context, pushes to wrong branch, and cannot detect its own changes aren't visible

Resolved 💬 3 comments Opened Apr 25, 2026 by rewired89 Closed Apr 28, 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?

Context Drift & Destructive Rewriting

Across multiple diverse projects, the model is exhibiting a consistent failure to maintain established architectural rules. There is a critical breakdown in Instruction Persistence, where the model successfully executes a complex task at the start but regressively destroys that progress during subsequent minor iterations.

  1. Core Technical Failures

Destructive Full-File Rewrites: Instead of performing targeted edits, the model frequently attempts "complete code overhauls" that wipe out stabilized features and logic not directly related to the current prompt.

Amnesiac Regressions: The model "forgets" foundational constraints (like custom UI positioning, specific naming conventions, or unique navigation rules) that were explicitly defined in the project memory.

"Junk Drawer" Logic: The model displays a tendency to consolidate independent system modules into single containers, breaking spatial and logical separation established in earlier prompts.

Generic Pattern Preference: The model repeatedly ignores specific, high-fidelity design mandates in favor of "standard/safe" web or software patterns (like reverting custom 3D logic to 2D UI dashboards).

  1. Functional Impact

Broken State Management: The model loses track of how different tiers or screens of an application interact, often resulting in "hollow" UI elements with no underlying logic.

Input/Interaction Deadlocks: Navigation logic (e.g., custom keyboard shortcuts or click-events) is frequently overwritten by default browser/OS behaviors during unrelated updates.

Instruction Timeout: Attempting to force the model to fix these systemic regressions often leads to "API Stream Idle Timeouts" as it struggles to reconcile its generic defaults with the user's complex instructions.

In other words, you are wasting user's money and time.
Hope you can fix the problems.
Thank you

What Should Happen?

The opposite of the report xD

Error Messages/Logs

Steps to Reproduce

He's not doing what user is asking it to do. I can't share my chat or project with you for now. Hope you can fix the problems by the full detailed report I just gave you.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.76 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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