fix: worktree threads keep their worktree when the agent starts, and messages sent during setup queue by maria-rcks · Pull Request #17654 · pingdotgg/t3code

fix(web): messages sent during worktree setup queue instead of being refused

maria-rcks

committed

2540f80

fix: hold follow-ups when worktree setup fails and let mobile queue during setup

maria-rcks

committed

c7e0fbf

fix: hold follow-ups when setup is interrupted and release them on retry

maria-rcks

committed

3dbeab4

fix(server): a setup retry only releases holds from its own failure

maria-rcks

committed

ade9163

fix(web): starting a worktree thread no longer resets it to the base branch

maria-rcks

committed

e0d5f88

fix(web): an automatic base-branch default only applies to an empty thread

maria-rcks

committed

b468f3e

fix(server): a follow-up queued during setup that arrives after it failed is held

maria-rcks

committed

4adf22e

Merge remote-tracking branch 'origin/main' into t3/wait-for-worktree-ready

maria-rcks

committed

570168d

fix(server): hold a late queued follow-up after an interrupted setup too

maria-rcks

committed

92adc8b

test(server): interrupt cases wait until setup is blocked in fetch

maria-rcks

committed

788e2d9

fix(mobile): a message sent during worktree setup is sent as queued

maria-rcks

committed

badb634

fix(mobile): setup detection also reads the thread runtime before detail loads

maria-rcks

committed

579ea42

Navigation Menu

Repository navigation

fix: worktree threads keep their worktree when the agent starts, and messages sent during setup queue - #17654

fix: worktree threads keep their worktree when the agent starts, and messages sent during setup queue#17654
maria-rcks merged 12 commits into
pingdotgg:mainfrom
maria-rcks:t3/wait-for-worktree-ready

Commits on Oct 10, 2026

fix(web): messages sent during worktree setup queue instead of being refused

fix: hold follow-ups when worktree setup fails and let mobile queue during setup

fix: hold follow-ups when setup is interrupted and release them on retry

fix(server): a setup retry only releases holds from its own failure

fix(web): starting a worktree thread no longer resets it to the base branch

fix(web): an automatic base-branch default only applies to an empty thread

fix(server): a follow-up queued during setup that arrives after it failed is held

Merge remote-tracking branch 'origin/main' into t3/wait-for-worktree-ready

fix(server): hold a late queued follow-up after an interrupted setup too

test(server): interrupt cases wait until setup is blocked in fetch

fix(mobile): a message sent during worktree setup is sent as queued

fix(mobile): setup detection also reads the thread runtime before detail loads