[Bug] /fork fails with "No conversation to fork" after EnterWorktree

Bug Description
/fork fails in entered worktree

• What's Wrong?: Running /fork after entering a worktree via EnterWorktree mid-session produces "Failed to fork conversation: No conversation to fork", even though the conversation is active.
• What Should Happen?: /fork should recognize the active conversation and fork it normally regardless of worktree state.
• Steps to Reproduce:

1. Start a new Claude Code conversation
2. Enter a worktree using EnterWorktree
3. Run /fork
4. Observe error: "Failed to fork conversation: No conversation to fork"

Environment Info

• Platform: darwin
• Terminal: WarpTerminal
• Version: 2.1.74
• Feedback ID: 898e1e6b-668c-4744-9127-c6d16ff93bc5

Errors

[{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/src/entrypoints/cli.js:81:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-12T15:03:41.001Z"},{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/src/entrypoints/cli.js:81:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-12T15:03:41.064Z"},{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/src/entrypoints/cli.js:81:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-12T15:03:42.518Z"},{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/src/entrypoints/cli.js:81:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-12T15:04:09.778Z"},{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/src/entrypoints/cli.js:81:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-12T15:04:14.540Z"},{"error":"Error\n    at CI (/$bunfs/root/src/entrypoints/cli.js:74:1144)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:79:10023)\n    at emit (node:events:92:22)\n    at endReadable…

Note: Content was truncated.

Workaround

Exit the session, and --resume it.