Repository navigation
fix(cursor): background commands survive the turn and wake the agent when they exit - #38187
Closed
Yash-Singh1 wants to merge 2 commits into
Closed
Yash-Singh1 wants to merge 2 commits into
Yash-Singh1 wants to merge 2 commits into
Conversation
…when they exit Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…urce-exhausted # Conflicts: # apps/server/src/mcp/McpInvocationContext.ts # apps/server/src/provider/agentContextBudget.json
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Collaborator
Author
|
Note Generated by Claude Fable 5.2 Renaming the head branch closed this PR. It continues unchanged in #38348. |
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 Cursor agent that started a background command (a build, a test run, a watcher) and said it would wait never heard back. The Cursor SDK kills an agent's background shells when the run ends and drops their completions, so the thread sat idle and nothing woke it.
t3_background_waitwas also unavailable on Cursor, and its description had to name the providers it worked on.Fix
awaitBackgroundTasksandstopTask, sot3_background_waitmarks the thread as waiting.tools.supportsBackgroundWait, andt3_background_waitis only listed for sessions whose provider supports it (Claude, Cursor, OpenCode). The provider list is gone from the tool description.t3_background_wait.Verification
composer-2.5against an isolated dev server: the agent is woken after the turn ends, the thread shows as waiting aftert3_background_wait, and Stop kills the command without a wake. A scripted prompt set passed 24/24 before the gating change and 8/8 after.mcp-tool-useeval was not run (no API key available locally).Claude Fable 5.2, Claude Code in T3 Code
🤖 Generated with Claude Code