[Bug] Fork session (/btw) continues task execution in original terminal instead of isolating to forked session

Bug Description
when doing fork from /btw, it continues there in the terminal. I want to be able to get the resume command to new terminal and work there. I want current terminal to continue working on whatever task is ongoing.

But even worse, the ongoing task keep working within the forked session - that is really a mess

see this:

● Update(.)
⎿  Removed 15 lines
124
...
129 <span>v{currentVersion ?? 1}</span>

❯ when working with the gitlab issues, don't create new labels. Use existing. For issue just created, fix it

● Got it — for future GitLab issues, only use existing labels (no new label creation).

For the issue just created (#44 "Re-implement click-to-edit in admin page builder against data-block-id"), the
labels applied were frontend,admin-ui,page-builder,follow-up — these likely included new labels that didn't exist.

To fix it, the labels field on the issue needs to be cleared or replaced with existing repo labels. Without tool
access I can't see the current repo label set or PATCH the issue, but the fix is:

curl --location --request PUT \
--header "PRIVATE-TOKEN: [REDACTED] \
--header "Content-Type: application/json" \
--data '{"labels": ""}' \
...

(or replace "" with a comma-separated list of labels confirmed to exist in the repo, e.g. after listing via GET
/projects/.../labels).

❯ /btw when working with the gitlab issues, don't create new labels. Use existing. For issue just created, fix it
⎿ Branched conversation "btw: when working with the gitlab issues, don't create new labels. Use existing…
(Branch)". You are now in the branch.
To return to the original: /resume 66ff5f0f-057d-43e2-a81b-187c5ddc06f2
(or from a new terminal: claude -r 66ff5f0f-057d-43e2-a81b-187c5ddc06f2)

● Update(f..)
⎿  Removed 1 line

● Update(..)
⎿  Removed 21 lines
342
343
354 -
355 - …
Note: Content was truncated.