6 people reported

All time, since Oct 2, including 2 thumbs-up on GitHub.

Auto-compaction loses session context

“Claude Code's automatic context compaction runs mid-session with no user consent or confirmation prompt.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/421/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 3 a week at the early-October peak.

Auto-compaction loses session context without warning or consent. Compression fires automatically when the context window fills, with "no pause" or prompt, dropping configuration details and in-progress task state.

Is this your bug?

File my report
Where
context compaction
Versions
2.1.201 to 2.1.258
Platforms
Linux, Windows
How bad
Loses work: code or files lost or damaged. Some reports say it used to work.

Part of: Auto-compaction loses session context6 bugs

  1. Autocompact thrashing ends session3 people
  2. Auto-compaction fires early3 people
  3. Idle auto-compaction35 people
  4. Idle after compaction2 people
  5. Opus 4.6 context capped at 200K12 people

Not quite your bug?

  1. Unauthorized edits despite rules14 people

Original reports4, newest first

  1. Session context lost during auto-compact, forcing restart of development workflow#100710
  2. Auto-compaction runs without user consent and degrades quality of long sessions#99860
  3. This "Claude ran out of context on this turn" is really common i am facing this…#99612
  4. Context exhaustion + Write tool overwrote append-only file — full day of design work lost#98967

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.