#Shared Session Chat Forking Is Broken and Blocking My Teams Work

1 messages · Page 1 of 1 (latest)

tacit fulcrumBOT
#

Hi @knotty zinc. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

You’re running into a known, currently open bug with shared-session chat forking in Warp.

From the reports we have, the behavior matches exactly what you describe:

  • Forking a chat that belongs to another account (or previously belonged to another user, e.g., via the same local SQLite DB) appears to work at first.
  • As soon as you send the first message in the forked chat, Warp throws an error and the chat becomes unusable.
  • This happens on Windows 11 with recent Warp versions and is reproducible when forking from shared sessions or chats that originated from another user. [Shared fork bug; Fork from shared session]

Warp engineers have acknowledged this as a regression and indicated they understand the likely cause and are working on a fix. [Shared fork bug] However, the knowledge sources do not provide a timeline, workaround, or confirmed resolution yet.

Given the current information:

  • Yes, this is a real, tracked bug.
  • Yes, it is recognized as blocking for teams relying on shared sessions and chat forking.
  • No reliable in‑product workaround is documented in the sources (e.g., there’s no confirmed way to safely continue those long-running chats from another account without hitting the error).

To help get it prioritized and tied directly to your case, the best next step (based on what we know) is:

#

  1. Add your details (OS, Warp version, how you reproduce it, and that it blocks your team) to the existing GitHub issues rather than opening a new one:

  2. If you haven’t already, also send feedback from within Warp with logs attached (the GitHub issue template links to log instructions), referencing those issue numbers so the team can correlate your case. [Fork from shared session]

I’m sorry I can’t offer a concrete workaround from the current knowledge sources; they only confirm the bug, its impact, and that a fix is being worked on, not how to bypass it safely today.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@knotty zinc Kapa.ai is still learning and improving, please let me know how I did by reacting below.