Show when a run was stopped or interrupted, and tell the agent
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- typescript
調査の方向性
Start from the timeline entry for a stopped run and from the path that sends the previous run's state into the agent's next turn. The payload names the desktop_insert entry with stopReason: aborted and the Stop action, but no source files, so locate those in the repo first. Done means three things: a stopped run shows who stopped it and when, a partial tool call is labeled as not run, and the next turn says the run was stopped or interrupted by a restart. Scope is cross-cutting, so confirm the approach in the thread before writing code.
索引モデルが issue の本文から書いたものです。
説明
Found in the desktop tools study (#427), D3 and D3b on Canary 0.0.46+684262d. Stopping and restarting worked: nothing was replayed, and an interrupted action was left as unknown. What the timeline shows doesn't match that.
Observed:
- After the owner presses Stop during a desktop run, the timeline shows the last tool calls as ordinary results, and nothing says the run was stopped. Tester confusion 1/3.
- In the next turn, the agent doesn't know its previous run was stopped by a person. It said: "Neither run hit an error or refusal on my side… I can't see why it stopped; my guess is the run was halted from outside."
- When the channel's worker is killed while the model is still writing a tool call, the partial call (arguments without
text,stopReason: aborted) shows as a reddesktop_insertentry with "Stopped.". It opens to nothing. The run then resumes after the worker restarts, and its summary ("Worked for 2 minutes 8 seconds") doesn't mention the restart. Tester confusion 2/3.
Expected:
- A Stop leaves a visible marker: who stopped it, when, and which in-flight action ended as unknown.
- The agent's next turn includes a note that the previous run was stopped by its owner, or interrupted by a restart.
- A tool call that never ran is labeled as such, for example "not run: the agent was interrupted while writing this call", and a resumed run says it resumed.
Part of #427.
- 主要言語
- TypeScript
- スター
- 1
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
githubnext/ace2 のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 94/100
githubnext/ace2#487 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
githubnext/ace2#486 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
githubnext/ace2#459 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
githubnext/ace2#437 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 40/100
githubnext/ace2#440 ·
githubnext/ace2 の issue をすべて見る
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
521xueweihan/HelloGitHub#4025 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
voidzero-dev/void#478 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 69/100
Small-tailqwq/dsh-deep-whale#207 ·
メンテナーはふだん 1 日以内に返信
-
The inspector never shows the instances field, so scaling out is unreachable対応中かも @Mrkewl が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
xevrion/breakscale#96 ·
メンテナーはふだん 4 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
Flux159/mcp-server-kubernetes#384 ·