Repository navigation
Conversation
… default With T3CODE_BACKGROUND_COMMANDS_HOLD=1, a Claude background command counts as awaited unless the agent releases it with t3_background_wait waiting:false (a dev server, a watcher). A thread whose agent waits on a deploy or CI command then stays in Working as Waiting, matching its "Waiting on 1 command" footer, even when the agent never marked it. Off by default; upstream behaviour is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
omar7550
force-pushed
the
feat/background-commands-hold
branch
from
November 17, 2026 16:57
c40b205 to
7db8c75
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A thread whose agent waits on a background command (a deploy, a CI wait) left the sidebar's Working section as soon as its turn ended. Its footer still read "Waiting on 1 command", but the command only held the thread when the agent had called
t3_background_wait. Agents often skip that call, so with 10 to 15 threads running, waiting threads mixed into the finished list.Upstream deliberately does not hold unmarked commands, because a dev server or watcher looks the same (pingdotgg#27355 was closed for that reason). So this is an opt-in local patch, not an upstream proposal.
Change
With
T3CODE_BACKGROUND_COMMANDS_HOLD=1in the server's environment, the Claude adapter publishes every background command as awaited unless the agent released it witht3_background_waitwaiting: false. The clients' existing rule then keeps the thread in Working as Waiting until the command ends. This needs no client change, so the desktop and phone apps both pick it up from the server. Monitors and subagents keep their current behaviour. Without the variable nothing changes.Verification
holds background commands by default when T3CODE_BACKGROUND_COMMANDS_HOLD is on: two unmarkedlocal_bashtasks are published as awaited, and releasing one withwaiting: falsepublishes it unawaited.ClaudeAdapterV2.test.tspass, and server typecheck, lint, fmt and knip are clean.local/nightly-patchedstack.Supersedes #2, the client-side version of this fix.
Written with Claude Code (Claude Opus 5.5).
🤖 Generated with Claude Code