[BUG] Instant auto-compaction not instant - compaction takes same time as before v2.0.64
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?
Version 2.0.64 changelog states "Made auto-compacting instant", but the compaction step/process still takes the same amount of time as before. Currently on v2.0.65 and the issue persists.
When auto-compaction triggers (or when using /compact manually), the process duration is identical to pre-2.0.64 versions - there's no observable improvement in how quickly compaction completes. The feature advertised as "instant"
has no noticeable performance difference.
What Should Happen?
Per the v2.0.64 changelog: "Made auto-compacting instant"
The compaction process should complete significantly faster (ideally instantly or near-instantly) compared to previous versions where it would take noticeable time to process and summarize the conversation context.
Error Messages/Logs
No error messages - the feature just doesn't behave as advertised.
Compaction completes successfully but takes the same duration as pre-2.0.64 versions.
Steps to Reproduce
- Use Claude Code v2.0.64 or later (tested on v2.0.65)
- Start a conversation and accumulate context until it reaches ~80% or triggers auto-compaction warning
- Either wait for auto-compaction to trigger OR run /compact manually
- Observe that the compaction process takes the same amount of time as it did in previous versions
- Expected: "Instant" compaction as per changelog
- Actual: Same duration as before the "instant" feature was introduced
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.0.65 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
- The v2.0.64 changelog explicitly states "Made auto-compacting instant" as a feature
- Issue persists in v2.0.65, suggesting the "instant" optimization is either not active or has a bug
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
The reported issue is different and new.
This is an issue I'm also having. Thought it would /compact instant, but it takes the same ammount of time as before (i'm on 2.0.67). Do we need to configure something?
Also, this is NOT a duplicate. It's a new feature and it's not working at the moment.
According to the instant compaction feature (v2.0.64+), the following should be happening but is not occurring on my machine:
Environment:
macOS user confirming this issue with additional diagnostic findings.
Environment:
Key Finding - Session Memory File Location:
The instant compact feature writes incremental summaries to:
~/.claude/projects/[project-path]/[session-id]/session-memory/summary.md
Evidence of intermittent functionality:
I have working examples from when the feature was active (Dec 11-12). These files contain detailed session summaries with sections like: Session Title, Current State, Task Specification, Files and Functions, Errors & Corrections, Learnings, Key Results, Worklog.
The problem:
Out of 900+ sessions in one project folder, only 1 has a
session-memorysubfolder. New sessions do not create this folder - the background summarization process isn't activating.Suspected cause:
I had multiple terminal windows running Claude Code simultaneously. Some terminals may have been running older versions while others had auto-updated. This version mismatch between concurrent sessions may have corrupted state or caused the feature to stop activating entirely.
What I've tried:
~/.claude/statsig/cachesession-memoryfolder - nothing gets written to itAdditional observation:
Auto-update from v2.0.67 to v2.0.68 occurred during troubleshooting. The feature was last working on v2.0.65 or earlier.
Expected behavior:
Each session should create a
session-memory/summary.mdfile that gets updated incrementally, making/compactinstant by using pre-built summaries.Actual behavior:
No
session-memoryfolder is created. Even when manually created, nothing is written to it./compactfalls back to slow full-conversation summarization (5+ minutes). The background process is completely dead.we rolled back instant auto compact. We will share our coms for when it is rolled back
FYI — this is behind a feature flag. If you have the Node version installed you can re-enable it, or even better you could partially reproduce the behavior by spinning up a background subagent triggered by a regular hook. If you already have a summary.md available, you can pass it into Claude to generate/update the instructions the agent uses to maintain that file. At that point your “instant compact” basically becomes: run
/clear, then/continue-sess, wherecontinue-sessis a custom slash command that just loads the previously saved session-memory file and resumes from it. Obviously this wouldn't work for you auto-compacters out there, unless you had the main Claude agent spin up a headless version of CC and do all its work through there instead of itself, directly, but that's another subject entirely. The point is, if you want something, the harness as it is, is almost certainly powerful enough to do the same thing in a different way.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.