claude-code - 💡(How to fix) Fix [FEATURE] Add context window usage indicator and warning before auto-compaction

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Claude Web retains conversation history across sessions. Users migrating from Claude Web to the desktop app expect similar reliability. Silent context loss without warning breaks trust and discourages long-term project use.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When a session's context window approaches its limit, Claude Code silently triggers auto-compaction with no prior warning to the user. From the user's perspective, the conversation history simply disappears — with no countdown, no icon, no alert. This is especially disruptive for long, multi-step project sessions where losing context mid-work causes real productivity loss and confusion.

Proposed Solution

Expected Behavior

  • A visible indicator (progress bar, icon, or badge) showing current context usage
  • A warning notification when context is near saturation (e.g., at 70–80%)
  • Optional: prompt the user to save a handoff note or summary before compaction occurs

Current Behavior

No indicator or warning exists. Auto-compaction happens silently.

Why This Matters

Claude Web retains conversation history across sessions. Users migrating from Claude Web to the desktop app expect similar reliability. Silent context loss without warning breaks trust and discourages long-term project use.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING