# [CRITICAL] Auto-compact triggers at 8-12% context making Claude Code unusable
Status Fixed / completed
Maintainer reply ✓ Yes — sid374
Workaround ✓ Mentioned in thread ↓
Activity 14 comments · opened Aug 19, 2025 · closed Aug 20, 2025
💡 Likely answer: A maintainer (sid374, contributor)
responded on this thread — see the highlighted reply below.
[CRITICAL] Auto-compact triggers at 8-12% context making Claude Code unusable
Bug Description
Claude Code version 1.0.84 has a critical auto-compact bug that renders the application completely unusable. The auto-compact triggers when context is at 8-12% instead of 95%+, causing constant interruptions every few minutes.
Environment
- Claude Code Version: 1.0.84 (Claude Code)
- Operating System: macOS (arm64)
- Terminal: zsh
- Subscription: Claude Code MAX $100/month
- Project Type: Next.js + Flutter monorepo
Steps to Reproduce
- Open Claude Code in any project directory
- Start any conversation
- Observe "Context left until auto-compact: 8-12%" appears immediately
- Auto-compaction triggers every 2-3 interactions regardless of actual context usage
Expected Behavior
- Auto-compact should only trigger at 90-95% context usage
- Auto-compact disabled in
/configshould be respected - Long development sessions should be possible without constant interruptions
Actual Behavior
- Auto-compact triggers at 8-12% context
- Setting auto-compact to "false" in
/configis ignored - Every conversation gets interrupted by forced compactions
- Makes Claude Code completely unusable for professional development
Troubleshooting Attempted
- ✅ Complete
~/.claude/directory reset - ✅ Downgrade to v1.0.83 (auto-update forces back to 1.0.84)
- ✅ Disabled auto-compact in settings (ignored)
- ✅ Removed large files from project
- ✅ Set
CLAUDE_CODE_DISABLE_AUTOUPDATER=true(ineffective) - ✅ Tested in empty directory (problem persists)
- ✅ Multiple
/clearcommands
Additional Information
- The bug appears to be specific to v1.0.84
- Auto-update cannot be disabled, forcing users to stay on buggy version
- This makes a $100/month service completely unusable
- Multiple users seem affected based on similar reports
Impact
- Critical: Cannot complete any meaningful development work
- Financial: Paying for unusable service
- Productivity: Constant workflow interruptions
Requested Actions
- Immediate hotfix for auto-compact threshold bug
- Respect auto-compact disabled setting
- Allow proper auto-update disabling
- Refund affected users for service downtime
This is a service-breaking bug that needs urgent attention.
14 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
@Dimitri-Jacquin thanks for the report. Could you take these steps to help debug this issue:
/bugand share thefeedback_idhere@sid374 2a25dffe-df60-4067-a50f-f2de17aa0752
UPDATE - Issue appears resolved after session reset
@sid374 Thanks for looking into this. I wanted to provide an update on my situation:
What worked:
Current status:
Key insight:
It seems like the bug was tied to my Claude session state. Once my 5-hour quota expired and reset, Claude Code started working properly again with auto-compact disabled.
Current workaround:
/compactwhen neededFeedback ID:
2a25dffe-df60-4067-a50f-f2de17aa0752This suggests the issue might be related to session state management between Claude Code and the main Claude service. Worth investigating if others experience similar resolution after session resets.
FR -> Ce commentaire explique clairement votre situation actuelle et pourrait aider d'autres utilisateurs ayant le même problème. Il suggère aussi une piste d'investigation intéressante pour les développeurs concernant la gestion des états de session.
Thanks for sharing the transcripts! We have some fixes in
1.0.85that should help. Please feel to reopen if you're still seeing issuesUpdate: The issue had temporarily disappeared but has now returned. The auto-compact bug is once again triggering at 0-6% context usage, making Claude Code v1.0.84 unusable again.
@Dimitri-Jacquin did you try 1.0.85?
Also how are you calculating 0-6%? Can you describe the behavior you're seeing in more detail please?
================================================= Previous Conversation Compacted =================================================
⏺ Compact summary (ctrl+r to expand)
⎿ Read components/notifications/notification-provider.tsx (324 lines)
⎿ Read app/api/v2/stripe/customer-portal/route.ts (93 lines)
⎿ Read app/api/v2/notifications/delete/route.ts (106 lines)
⎿ Todo list read (8 items)
-->Context left until auto-compact: 3%
-->dimitrijacquin@macstudio-de-dimitri web-app % claude --version
1.0.85 (Claude Code)
Compact summary (ctrl+r to expand)
⎿ Read components/notifications/notification-provider.tsx (325 lines)
⎿ Read package.json (96 lines)
⎿ Read app/api/v2/stripe/customer-portal/route.ts (93 lines)
⎿ Read app/api/v2/notifications/delete/route.ts (106 lines)
⎿ Todo list read (12 items)
-->Context left until auto-compact: 0%. --> Game over (100$ plan...)
I am seeing this as well on v1.0.89. Everytime Claude auto-compacts, it resets the compact limit to 4-6% for me. Basically causing it to auto-compact every few file reads/lookups.
Session ID: 8dec1375-d4b0-4f38-b679-83ad1282d743
Same for me on v1.0.89. Auto compacts every so often and forgets what it's doing. This renders it practically unusable
Found a "fix." Not sure how detrimental it is to context awareness, but deleting/renaming the settings.local file in the .claude folder fixed the context issues for me. I am guessing the file just got too large for Claude to be able to effectively read because of all the bash commands it stored away that weren't reusable in most cases.
if you want to YOLO it, you can use "claude --dangerously-skip-permissions" to bypass permission prompts (the ones that when saved to the project, fill up the setting.local.json file and ultimately cause the context issue)
But that is absolute last resort and very dangerous to do. Hence the flag name....
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.