Standalone tools.execute calls keep failing after session abort until another chat turn

オープン
  • 何か問題がありますか？
#2,871 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
node.js, python, typescript
領域
api, backend

調査の方向性

Start with the SDK's session.rpc.abort and session.rpc.tools.execute handling, then trace how cancellation state is created and cleared across direct calls and chat turns. Use the attached abort-repro.zip and its baseline, resume, and recovery runs to reproduce the failure; done means a standalone call after abort reaches the MCP server without a model turn, and standalone completion has a documented or exposed idle signal.

索引モデルが issue の本文から書いたものです。

説明

After a joined extension calls session.rpc.abort({reason:'remote_abort'}), the running session.rpc.tools.execute is cancelled as expected. But the next standalone call, with a fresh toolCallId, is also rejected before it reaches the MCP server:

code: -32603
Request session.tools.execute failed with message: Tool execution was aborted.

Reproduced on Linux x86_64 with Copilot CLI 1.0.103, Node SDK 1.0.26, and Node 25.9.0. No agent turn is running when the extension starts the tool. The SDK's current main (c57638f4) has the same abort/execute contract as 1.0.26.

Repro

The attached abort-repro.zip contains a tiny joined extension, local Python MCP wait tool and launcher. Each run creates a private COPILOT_HOME. With Node, Python 3 and authenticated Copilot CLI available:

abort-repro.zip

npm install --no-save --package-lock=false @github/[email protected]
node repro.mjs baseline
node repro.mjs resume resume
node repro.mjs recovery send
  1. The extension successfully executes the local wait tool as a control.
  2. It starts a longer call and aborts on the first matching progress event.
  3. Abort returns {success:true}. The MCP server receives cancellation and finishes.
  4. Calls after 500 ms and 3.5 seconds fail with the error above, without reaching the server. Rejection takes roughly 2–7 ms.
  5. Resuming the still-active session does not restore execution. One explicit chat turn replying OK does; the next tool call reaches the same server and succeeds. The send run makes that real model turn.

After cancellation, metadata reports processing:false, abortable:false, hasActiveWork:false. This reproduced with both the CLI-bundled SDK and the published SDK package. It appears that direct calls retain an aborted cancellation scope, but I have not identified the native state responsible.

Expected / ask

The next explicit standalone invocation should have a usable cancellation scope. Could tools.execute support per-request cancellation, or could the SDK expose a supported way to clear the aborted state without running a model turn? SDK #1433 is related, but concerns cancellation reaching client handlers; here MCP cancellation already reaches the server.

Separately, successful direct execution before any abort emits no session.idle in the following one-second observation, although all activity flags are false. A completed chat turn does emit it. Please also document/provide the standalone completion signal so session indicators can return to idle when no work remains. I do not assume this lifecycle gap and the abort failure have the same cause.

主要言語
Java
スター
10.7k
フォーク
1.5k
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/copilot-sdk のほかの issue

github/copilot-sdk の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。