Pi continuation runs in original checkout after worktree handoff #36570

What happened

After asking Pi to move an existing thread into a new worktree, T3 selects the worktree but Pi continues running commands in the original checkout.

Diagnosis

Read-only thread records confirm a queued continuation ran pwd and git branch in the original checkout, while the T3 thread was bound to the new worktree. A later turn did the same. WorktreeMcpService intends to detach the old provider session and resume in the worktree. SelectionRestart.integration.test.ts checks the requested cwd with a test adapter, not a live Pi session. Root cause is not established.

Steps to reproduce

1. Open a Git project in the local T3 desktop app and start a Pi thread in the original checkout.
2. Ask Pi to move the current thread to a new worktree, using t3_worktree_handoff with a continuationPrompt to run pwd and git branch --show-current.
3. Compare the continuation output with the worktree selected by T3.
   Expected: Pi runs in the new worktree and branch. Actual: Pi runs in the original checkout and branch. Observed once; not independently reproduced in a clean installation.

Version

0.1.10-nightly.20261114.4669

Environment

macOS 27.0.0 arm64, local T3 Code Desktop nightly and server, Node v24.22.1, Pi provider.

Evidence

2026-11-14 07:54 UTC: handoff requested branch toeter with continuation. T3 thread projection bound to the toeter worktree. Continuation bash: pwd; git branch --show-current returned the original checkout and master. A later turn returned the same. Paths redacted. The handoff tool item was recorded interrupted; the calling run and continuation run were completed.

Related issues

#22971 has an earlier user comment reporting a Pi checkout mismatch; it primarily concerns Claude continuation failures. #21573 concerns a Pi provider error after handoff. PR #36360 explicitly did not investigate Pi remaining in the old checkout without continuation; this case has a continuation.

Fix applied or workaround

No fix applied. Start a new thread in the intended worktree or use explicit worktree paths and verify pwd before changes; neither workaround was tested in this investigation.

Filed by

Pi with openai-codex/gpt-6.1-terra via T3 Code triage