Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [SYS-029] Claude Desktop: no compact/continue option when conversation hits context limit [4 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#48964•Fetched 2026-04-17 08:54:34
View on GitHub
Comments
4
Participants
2
Timeline
4
Reactions
0
Author
ThatDragonOverThereThatDragonOverThere
Participants
github-actions[bot]github-actions[bot]ThatDragonOverThereThatDragonOverThere
Timeline (top)
commented ×4

When a Desktop conversation hits the context limit, Desktop shows a hard wall:

"This conversation is too long to continue. Start a new chat, or remove some tools to free up space."

There is no option, no autocompact, and no way to continue the session. The entire conversation is permanently lost for practical purposes.

Root Cause

When a Desktop conversation hits the context limit, Desktop shows a hard wall:

"This conversation is too long to continue. Start a new chat, or remove some tools to free up space."

There is no option, no autocompact, and no way to continue the session. The entire conversation is permanently lost for practical purposes.

Fix Action

Workaround

Use plain CLI window instead of Desktop for long-running agent sessions. and work in CLI.

RAW_BUFFERClick to expand / collapse

Summary

When a Desktop conversation hits the context limit, Desktop shows a hard wall:

"This conversation is too long to continue. Start a new chat, or remove some tools to free up space."

There is no option, no autocompact, and no way to continue the session. The entire conversation is permanently lost for practical purposes.

Expected Behavior

Claude Desktop should offer the same context management options that CC CLI provides:

  • command to summarize and continue
  • behavior when context is running low
  • Or at minimum: a warning before the limit is hit so the user can manually compact

Actual Behavior

Hard wall with no recovery. User must start a new chat and re-paste all context manually.

Impact

  • Long-running Desktop sessions (PM agents, overnight analysis) are permanently killed when context limit hits
  • Disproportionately impacts agentic workflows where sessions accumulate context over hours
  • For a multi-hour overnight PM agent session, this is equivalent to a hard crash with no checkpoint
  • CLI (CC) users have and — Desktop users have nothing

Reproduction

  1. Start an agentic session in Claude Desktop
  2. Run a long session (overnight agent, heavy tool use, etc.)
  3. Observe: when context limit is reached, Desktop shows the hard wall message
  4. No compact, no continue, no warning — session is dead

Environment

  • Desktop 1.2581.0 (Windows 11 Pro x64)
  • Also confirmed on 1.2278.0
  • Persists after upgrade to latest Desktop version (tested 2026-04-15)

Related

  • CC CLI has and that keep sessions alive — Desktop lacks both
  • Related to Desktop renderer crashes (#44558) which also kill long sessions prematurely

Workaround

Use plain CLI window instead of Desktop for long-running agent sessions. and work in CLI.

extent analysis

TL;DR

Implement a context management system in Claude Desktop similar to the CC CLI, including options to summarize and continue conversations, or provide a warning before the context limit is reached.

Guidance

  • Investigate the feasibility of integrating the CC CLI's context management features, such as the compact command, into Claude Desktop to prevent session loss.
  • Consider adding a warning system to alert users when the context limit is approaching, allowing them to manually compact or manage their conversation history.
  • Review the related issue #44558 regarding Desktop renderer crashes, as resolving this may also help prevent premature session termination.
  • Evaluate the potential for implementing an autocompact feature or automatic context summarization to mitigate the impact of reaching the context limit.

Example

No code example is provided as the issue does not specify the exact implementation details of the CC CLI's context management features.

Notes

The provided workaround suggests using the plain CLI window for long-running agent sessions, which may not be a suitable long-term solution for users who prefer the Desktop interface.

Recommendation

Apply a workaround by using the CC CLI for long-running sessions until a proper context management system is implemented in Claude Desktop, as this allows users to utilize the existing compact and summarization features to manage their conversations.

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…
#prompt formatting#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

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

Back to top recommendations

TRENDING