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
Commit 96dab59
Browse filesBrowse the repository at this point in the historyBrowse files
fix: a message you send resumes a held queue, and mobile can resume one
A stop or a restart holds the thread's queue until someone presses Resume.
Sending a new message started a run but left the hold in place, and every
subagent completion that queued behind that run inherited it, so an
orchestrating thread stopped hearing from its subagents for good. Mobile
had no way out: its queue sheet lists only the user's own messages, so a
queue holding only completion wakes showed nothing to resume.
A message the user sends from a client now releases the hold, so what was
held follows it. Server continuations after a usage limit or a restart do
not, and a missing worktree keeps its hold. Mobile's empty composer shows
Resume while the queue is held, as web's does.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments