Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); fix(server): keep Claude CLI alive across Stop by TONiiV · Pull Request #8997 · pingdotgg/t3code · GitHub
Skip to content

fix(server): keep Claude CLI alive across Stop - #8997

Closed
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session
Closed

fix(server): keep Claude CLI alive across Stop#8997
TONiiV wants to merge 1 commit into
pingdotgg:mainfrom
TONiiV:fix/claude-interrupt-keep-session

Conversation

@TONiiV

@TONiiVTONiiV commented Sep 1, 2026

Copy link
Copy Markdown

What Changed

Claude Stop (interruptTurn) no longer closes the provider query. It now:

  1. Stops live subagent tasks via Query.stopTask
  2. Calls Query.interrupt() and completes the local turn
  3. Keeps the CLI process so the next prompt is queued into the same session
  4. Falls back to close() only when live tasks remain (the fix(server): stop kills lingering Claude work #5891 runaway-fleet case)

thread.session.stop and the 30-minute idle reaper still tear the process down.

Why

#7338 reports ~2× Claude usage in T3 vs native Claude Code. After #5891, Esc killed the CLI. The next message --resumes a new process.

A cheap local check (Haiku, --max-turns 1, prompt reply with just the word ok, 5h usage 0% → 1%):

turncache_writecache_read
1 cold24,53813,694
2 --resume, git unchanged26,84113,694
3 --resume after one untracked file26,94413,694

Each resume rewrote ~27k cache tokens even when git status did not change. On a 300k thread that is the cache-write spike reported in #7338. Native Claude Code keeps one process alive across Esc.

This does not claim to erase the whole gap. Claude effort/fast-mode changes still restart the session, idle reaping still stops it after 30 minutes, and app restart still --resumes. Those are separate.

Test plan

  • vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts (81 passed)
  • Esc mid-turn, send a follow-up: session stays, usage should not jump as a full resume
  • Esc while subagents are running: live tasks stop; if they cannot, process still closes
  • Changing Claude effort still restarts (unchanged)

Made with Cursor

Note

Keep Claude CLI alive across Stop by interrupting turn and stopping live tasks

  • Reworks interruptTurn in ClaudeAdapter to cooperatively stop live subagent tasks via query.stopTask and cancel the in-flight turn via query.interrupt, instead of unconditionally closing the CLI session.
  • Emits task.completed events with status 'stopped' for acknowledged task stops, and completes the open turn as 'interrupted'.
  • Falls back to stopSessionInternal (closing the CLI) only when live tasks remain and stopTask is unavailable or ineffective.
  • Extends the ClaudeQueryRuntime interface to require interrupt() and optionally support stopTask(taskId).
  • Updates tests in ClaudeAdapter.test.ts and documents the new Stop semantics in providers.md.
  • Risk: any out-of-tree implementation of ClaudeQueryRuntime must now provide interrupt(); without it, type checking and runtime calls will fail.
📊 Macroscope summarized 4b1c76f. 2 files reviewed, 2 issues evaluated, 0 issues filtered, 2 comments posted

🗂️ Filtered Issues

Closing the query on Esc forced the next prompt through --resume, which
rewrites prompt cache. Interrupt the turn and live tasks instead, and
only close when background work cannot be stopped.
Co-authored-by: Cursor <cursoragent@cursor.com>
@TONiiVTONiiV mentioned this pull request Sep 1, 2026
2 tasks
@github-actionsgithub-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Sep 1, 2026
Effect.as(true),
Effect.catch(() => Effect.succeed(false)),
);
if (!stopAcknowledged || !context.liveTaskIds.delete(taskId)) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4636

A delayed concurrent interruptTurn can interrupt a newer turn after the original turn has already been stopped. The second call reaches context.query.interrupt() after its stopTask result is discarded, and _turnId is ignored; capture and re-check the requested turn identity before interrupting.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4636:
A delayed concurrent `interruptTurn` can interrupt a newer turn after the original turn has already been stopped. The second call reaches `context.query.interrupt()` after its `stopTask` result is discarded, and `_turnId` is ignored; capture and re-check the requested turn identity before interrupting.

yield* Effect.tryPromise({
try: () => context.query.interrupt(),
catch: (cause) => toRequestError(threadId, "turn/interrupt", cause),
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 HighLayers/ClaudeAdapter.ts:4673

A subagent that starts during query.interrupt() is left running, and the Claude CLI stays alive instead of taking the stopSessionInternal() fallback. The liveTaskIds check occurs only before the interrupt, so recheck it after query.interrupt() and close the session if a task was added.

🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/server/src/provider/Layers/ClaudeAdapter.ts around line 4673:
A subagent that starts during `query.interrupt()` is left running, and the Claude CLI stays alive instead of taking the `stopSessionInternal()` fallback. The `liveTaskIds` check occurs only before the interrupt, so recheck it after `query.interrupt()` and close the session if a task was added.

@cursorcursorBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover interrupt result closes next turn

Medium Severity

interruptTurn locally completeTurns after Query.interrupt() acknowledges, but the SDK still emits the interrupted result (and sometimes a truncated assistant message) on the live stream. handleResultMessage completes whatever turnState exists, so a follow-up sendTurn can be closed as interrupted. If those leftovers arrive before the next send, handleAssistantMessage also auto-starts a synthetic working turn.

Additional Locations (2)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.


if (context.turnState) {
yield* completeTurn(context, "interrupted");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interrupt leaves pending requests open

Medium Severity

Cooperative Stop no longer runs the pendingApprovals and pendingUserInputs teardown that lived in stopSessionInternal. After Esc, completeTurn marks the turn interrupted while request.opened and user-input.requested can stay unresolved, so approval or AskUserQuestion dialogs remain on a finished turn.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit 4b1c76f. Configure here.

@macroscopeapp

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production Claude Stop path from closing the CLI to coordinating subagent termination, interrupting the turn, and retaining the process, with new concurrency and lifecycle behavior. Unresolved concerns involve delayed interrupts, late SDK events, runaway tasks, and pending interactive requests, so the effects require human review.

Not approved because:

  • 2 blocking correctness issues found at or above your repo's Minimum Blocking Severity

Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.

@TONiiVTONiiV closed this Sep 1, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M30-99 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@TONiiV