claude-code - 💡(How to fix) Fix Session recap contains content from a different, unrelated conversation [1 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#51887Fetched 2026-04-23 07:42:15
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Root Cause

Because the leaked recap contained a PR number and a feature name from a different session, this appears to be a cross-session content leak. No secrets exposed, but the behavior crosses a session boundary that should not be permeable.

RAW_BUFFERClick to expand / collapse

What happened

In a Claude Code session, the UI surfaced a "recap" line summarizing work that was never done in the current conversation. The recap described a completely unrelated task — different topic, different PR number, different module/feature names than anything discussed in the active session.

When asked "is the recap correct?", the assistant correctly identified the mismatch and confirmed the recap did not reflect the current conversation.

Expected

The recap should reflect the current conversation, or be absent.

Actual

The recap referenced contents that must have come from a different session.

Environment

  • Claude Code: 2.1.117
  • Model: claude-opus-4-7[1m] (Opus 4.7, 1M context)
  • Platform: darwin (macOS, Darwin 24.6.0)
  • Shell: zsh
  • Context: long-running session; /clear had been used earlier in the conversation

Privacy note

Because the leaked recap contained a PR number and a feature name from a different session, this appears to be a cross-session content leak. No secrets exposed, but the behavior crosses a session boundary that should not be permeable.

Repro steps

Unknown — the user noticed the incorrect recap at the bottom of the terminal and flagged it. Possibly triggered by long-running sessions, /clear, or end-of-turn recap generation drawing from the wrong conversation state.

extent analysis

TL;DR

The issue can be mitigated by investigating the conversation state management in Claude Code sessions, particularly after using the /clear command.

Guidance

  • Investigate how the /clear command affects the conversation state and whether it properly resets the context for recap generation.
  • Review the session management logic to ensure that each session's context is properly isolated from others.
  • Consider adding logging or debugging statements to track the conversation state and recap generation process to identify where the cross-session content leak occurs.
  • Look into the claude-opus-4-7 model's documentation to see if there are any known issues or limitations related to conversation state management.

Example

No code snippet is provided as the issue does not contain sufficient technical details about the implementation.

Notes

The root cause of the issue is unclear, and more information about the conversation state management and recap generation logic is needed to provide a definitive fix. The provided guidance is based on the assumption that the issue is related to the conversation state management.

Recommendation

Apply workaround: Implement additional logging and debugging to track the conversation state and recap generation process to identify the root cause of the issue. This will help to understand where the cross-session content leak occurs and provide a basis for a more targeted fix.

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

claude-code - 💡(How to fix) Fix Session recap contains content from a different, unrelated conversation [1 participants]