Warp throwing error when forking a shared session chat (or a chat that has previously belonged to another user)

[Jarring0zx0]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

Whenever I fork the chat of a shared session from my friend or from some of my team members (so we can take off from where they left off), or in general just fork a chat that has belonged to another account (via the same sqlite database), Warp throws the error attached in the image at the bottom.

To reproduce

1. Have 2 Warp accounts ready, call them X and Y.
2. Create a chat on X, send a message or two and then create a shared session. Set permissions to Read or Edit to Y's email address.
3. Log in with Y and enter the shared link.
4. Try and fork the chat from Y's account.
5. Try and send a message in the forked chat from Y.

Result: error.

Expected behavior

I would have expected the chat to obviously work and should have let me fork it without any problems.

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

Windows 11

Shell Version

PowerShell 5.1.26100.7705

Current Warp version

v0.2026.02.11.08.23.stable_01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

12/02/2026

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[jefflloyd]

Thanks for the report - I think I know what's causing some issues here, I'll hopefully have a fix soon. Sorry for the regression!

[Jarring0zx0]

Hey there Jeff, thank you for assurance. 😁

[dr4gan0x]

Thanks for the report - I think I know what's causing some issues here, I'll hopefully have a fix soon. Sorry for the regression!

Thank you very much, we're waiting! My team and I are experiencing this issue and haven't been able to continue our projects for almost two days. We can't switch to a different AI IDE because there's a huge loss of context!

[dr4gan0x]

Yes, I agree. I haven’t been able to properly keep our shared work moving with my team for the past two or three days. I’ve been using WARP AI for over a year now, and this is easily the worst update they’ve ever pushed. If they don’t fix this within the week, my team and I will be moving our subscription back to Windsurf.

They seem very eager to schedule meetings for enterprise accounts, yet they can’t manage to reply to emails for an entire week. It honestly doesn’t feel sincere.

[jefflloyd]

I'm working on a fix as we speak and will try to ship it + update you all as soon as I can. This issue was reported on a Saturday and Monday was a holiday here in the US, so today is the first full day I can work on it (and have people online for code review, etc.); I appreciate your patience here.

[0xFar5eer]

I have the same problem here

[jefflloyd]

Merged a fix for this, it should be live tomorrow morning. I'll try and post another update when it's out.

[jefflloyd]

This should be live - can folks let me know if they see this come up again?

[dr4gan0x]

This should be live - can folks let me know if they see this come up again?

I'm testing it now. I'll let you know.

[dr4gan0x]

This should be live - can folks let me know if they see this come up again?

The issue is still ongoing on my side.
I'm using Windows 11 and Warp AI version v0.2026.02.11.08.23.stable_02.

The same error occurs both when forking a chat and when another user joins the same chat session.

Error message:

I'm sorry, I couldn't complete that request.
Request failed with error: ErrorStatus(400, "{"error":"Something went wrong with this conversation. Please try starting a new conversation."}")

Edit:
Is this version correct? I’ve been on this same version for the past ~10 days, and I don’t see any updates or changes in the changelog either. Just want to confirm whether a new fix has actually been released.

[0xFar5eer]

The error persists on macOS 26.3 and the warp version v0.2026.02.11.08.23.stable_02.

[jefflloyd]

Hmm. I'm gonna need more information then. Can you send me (either here or through my email - jeff [ at ] warp [ dot ] dev):

1. Emails of people involved
2. Any conversation IDs (you can right click on an Oz conversation and select "Copy debugging ID" to grab one)
3. Exact repro steps - the more precise the better. Something like, "I'm logged in as teammate1@gmail.com, and I created conversation abcd1234, and then I shared a session with teammate2@gmail.com, and he tried forking it on his computer, and he encounters the bug" - that level of detail will be helpful for me.
4. (Even better) A Loom or other screen recording of the issue happening

Make sure you have "Help improve Warp" turned on in Settings > Privacy (otherwise my visibility into what's going on is very very limited).

This is a server error, not a client one, so no need to worry about if your Warp is updated to the one released today - any client from the last month or so shouldn't have any issues.

[dr4gan0x]

Hmm. I'm gonna need more information then. Can you send me (either here or through my email - jeff [ at ] warp [ dot ] dev):

1. Emails of people involved
2. Any conversation IDs (you can right click on an Oz conversation and select "Copy debugging ID" to grab one)
3. Exact repro steps - the more precise the better. Something like, "I'm logged in as teammate1@gmail.com, and I created conversation abcd1234, and then I shared a session with teammate2@gmail.com, and he tried forking it on his computer, and he encounters the bug" - that level of detail will be helpful for me.
4. (Even better) A Loom or other screen recording of the issue happening

Make sure you have "Help improve Warp" turned on in Settings > Privacy (otherwise my visibility into what's going on is very very limited).

This is a server error, not a client one, so no need to worry about if your Warp is updated to the one released today - any client from the last month or so shouldn't have any issues.

Hi, just an update from my side.
The forking issue appears to be fixed now, i'm able to fork conversations without errors.
However, continuing the same conversation from a different account on the same device still results in the same error. If I log into another account and try to send a message in that existing conversation, the request fails.
This isn’t a major blocker for me personally, since my team mainly relies on the forking workflow. That said, this behavior did work previously. Even when switching accounts on the same device, existing conversations remained usable and writable without errors.
It seems there may still be an issue related to conversation ownership or ownership transfer when a conversation is accessed by a different account. Thank you for everything.