Session recap contains content from a different, unrelated conversation

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.