You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Claude run fails with "provider event stream closed unexpectedly" after t3_worktree_handoff (still on 0.1.2-nightly.20261021.3473) #22863
The provider event log shows the handoff tool_use at 12:01:23.395Z, then T3's own outgoing query.close at 12:01:27.436Z, and the run marked failed 2 ms later. So the session is ended by T3's planned detach, not by Claude Code crashing.
Screenshot:
Likely cause
The thread.metadata.update that changes worktreePath detaches every session on the thread (apps/server/src/orchestration-v2/Orchestrator.ts, detachSessionIds) without settling the active run. For single-thread providers, ProviderSessionManager.detach then releases with manual_shutdown, and failSubscribers hands the running turn a ProviderAdapterEventStreamError.
This matches the planned-detach failure tracked in https://git.cafe/pingdotgg/t3code/issues/15136: the worktree binding succeeds, then the handoff turn fails when T3 closes the Claude session (the failed run follows query.close by a few milliseconds in your log). Omitting continuationPrompt removes the queued-continuation symptom but leaves the same detach failure. Draft fix https://git.cafe/pingdotgg/t3code/pulls/22825 is pending review. Closing as a duplicate; that does not mean the fix has shipped, so please follow https://git.cafe/pingdotgg/t3code/issues/15136 for the release.
Activity
juliusmarminge commentedon Oct 21, 2026
This matches the planned-detach failure tracked in https://git.cafe/pingdotgg/t3code/issues/15136: the worktree binding succeeds, then the handoff turn fails when T3 closes the Claude session (the failed run follows
query.closeby a few milliseconds in your log). OmittingcontinuationPromptremoves the queued-continuation symptom but leaves the same detach failure. Draft fix https://git.cafe/pingdotgg/t3code/pulls/22825 is pending review. Closing as a duplicate; that does not mean the fix has shipped, so please follow https://git.cafe/pingdotgg/t3code/issues/15136 for the release.