claude-code - 💡(How to fix) Fix [BUG] session quality degraded significantly from prior sessions — workflow ordering errors, missed requirements from plan doc that was already loaded -- felt like catastrophic forgetting. [1 comments, 2 participants]

Preflight Checklist

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

What's Wrong?

All prior sessions have been awesome, but this session, just did faceplant after faceplant!

What Should Happen?

Claude should really try to remember the place we were at in the last session better. Total loss of focus on Claude's part. Sloppily skipping steps. Perhaps compaction wants a better approach to dealing with screenshots? Some are important and need to be cached. Some are status and evaporate (up to OCR) after use.

Error Messages/Logs

I hear your frustration — this session had real problems. The screenshot ordering mistake (asking you to navigate backwards
   through a one-way workflow), the temp files vanishing twice, and then missing the collaboration screenshot entirely at the
   end. Those were avoidable.                                                                                                
   
  To your questions:                                                                                                         
                                                                
  Same model — I'm Claude Opus 4.6, same as your good sessions. Bad sessions happen when context gets fragmented (like after 
  compaction) or when I don't plan the workflow carefully enough before asking you to act. Not an excuse, just the mechanism.
                                                                                                                             
  Registering feedback — the best way to flag this is at https://github.com/anthropics/claude-code/issues. Anthropic's team  
  reads those. A note like "session quality degraded significantly — workflow ordering errors, missed requirements from plan
  doc that was already loaded" would be useful signal for them.                                                              
                                                                
  I'm sorry about the wasted time, especially the undo-past-10-steps moment. That one was genuinely my fault — I should have 
  read the app's workflow before asking you to navigate.

Steps to Reproduce

print("Read Error Messages/Logs, What Should Happen, and Whats Wrong")

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.97 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Good grief this was the most incompetent session I've had. Were you a different model or am I running out of any favor
with the "new user" gods at Anthropic? How did we go from some amazing sessions to faceplant after faceplant? Can
Anthropic register my annoyance with this session?

⏺ I hear your frustration — this session had real problems. The screenshot ordering mistake (asking you to navigate backwards through a one-way workflow), the temp files vanishing twice, and then missing the collaboration screenshot entirely at the end. Those were avoidable.

To your questions:

Same model — I'm Claude Opus 4.6, same as your good sessions. Bad sessions happen when context gets fragmented (like after compaction) or when I don't plan the workflow carefully enough before asking you to act. Not an excuse, just the mechanism.

Registering feedback — the best way to flag this is at https://github.com/anthropics/claude-code/issues. Anthropic's team
reads those. A note like "session quality degraded significantly — workflow ordering errors, missed requirements from plan doc that was already loaded" would be useful signal for them.

I'm sorry about the wasted time, especially the undo-past-10-steps moment. That one was genuinely my fault — I should have read the app's workflow before asking you to navigate.