claude-code - 💡(How to fix) Fix [BUG] URGENT! EVERY CONVERSATION SEVERED -- Cowork: Live session severs mid-conversation — error on reply, then Claude receives message with zero prior context (macOS) [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#49582Fetched 2026-04-17 08:37:04
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×5

Error Message

During an active Cowork session (not across restarts, not across tab switches), replying to Claude's most recent message produces an error indicating the conversation cannot be found or recognized. After dismissing the error and resubmitting the same message, Claude receives it as the first message of a brand new session. All prior conversation context is gone. Claude has no memory of anything said in the session before that point.

Error Messages/Logs

I now get an error like this with EVERY SINGLE CONVERSATION !! 5. UI throws an error indicating the conversation is not recognized / cannot be found.

Fix Action

Fix / Workaround

The user has already lost visibility into the earlier portion of the conversation (UI truncation / compaction). Claude still had that history and could be asked about it (a viable workaround). When the session identity severs, Claude also loses the history. Neither party retains the conversation. The data is unrecoverable.

This is a full data loss scenario, not a rendering bug. The workaround for #42890 (asking Claude to recall what the user can no longer see) is destroyed by this bug.

Code Example

"No conversation found with session ID: a8201067-b6a8-4d39-a6be-e7c604124935

You can restart the conversation from an earlier message."

I now get an error like this with *EVERY SINGLE CONVERSATION* !!
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Description During an active Cowork session (not across restarts, not across tab switches), replying to Claude's most recent message produces an error indicating the conversation cannot be found or recognized. After dismissing the error and resubmitting the same message, Claude receives it as the first message of a brand new session. All prior conversation context is gone. Claude has no memory of anything said in the session before that point. This is not a UI rendering issue. The conversation history is not hidden; it is severed. Claude explicitly confirms it has no record of anything prior to the resubmitted message. The session identity itself is lost mid-conversation.

What Should Happen?

The reply should be appended to the existing conversation. Claude should receive it with the full conversation history intact and respond in context.

Error Messages/Logs

"No conversation found with session ID: a8201067-b6a8-4d39-a6be-e7c604124935

You can restart the conversation from an earlier message."

I now get an error like this with *EVERY SINGLE CONVERSATION* !!

Steps to Reproduce

  1. Open a Cowork session with a mounted project folder (macOS).
  2. Have a multi-turn conversation with substantial tool use (file reads, subagent delegation, memory writes, file creation). Session was approximately 60-90 minutes in.
  3. Claude sends a long response with analysis and file creation.
  4. User types a reply to that response.
  5. UI throws an error indicating the conversation is not recognized / cannot be found.
  6. User resubmits the same message.
  7. Claude receives the message with zero prior context and treats it as the start of a new session.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Can't find it

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Compound Failure with #42890 / #37273 This bug compounds with the known UI truncation issue (#42890) and compaction-triggered scrollback loss (#37273). In sessions where both occur:

The user has already lost visibility into the earlier portion of the conversation (UI truncation / compaction). Claude still had that history and could be asked about it (a viable workaround). When the session identity severs, Claude also loses the history. Neither party retains the conversation. The data is unrecoverable.

This is a full data loss scenario, not a rendering bug. The workaround for #42890 (asking Claude to recall what the user can no longer see) is destroyed by this bug.

extent analysis

TL;DR

The conversation session ID is lost mid-conversation, causing Claude to treat the next message as a new session, and a potential workaround is to investigate session management and ID handling in the Claude Code.

Guidance

  • Investigate the session ID generation and management in the Claude Code to ensure it is correctly handling and storing session IDs, especially during long conversations with substantial tool use.
  • Verify that the error message "No conversation found with session ID" is not related to a specific session ID format or validation issue.
  • Review the code changes between the last working version and the current version to identify potential regressions related to session management.
  • Consider implementing a temporary workaround, such as storing conversation history locally or using a different session management approach, to mitigate the data loss issue.

Example

No code snippet is provided as the issue lacks specific code details, but investigating the session ID handling in the Claude Code might involve reviewing functions or methods responsible for generating, storing, and retrieving session IDs.

Notes

The issue seems to be related to a regression, and the last working version is not specified, which makes it challenging to provide a precise fix. The compound failure with other issues (#42890 and #37273) adds complexity to the problem.

Recommendation

Apply a workaround, such as storing conversation history locally or using a different session management approach, as the root cause of the issue is not immediately clear and may require further investigation.

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