[Feature]: CLI - ACP: queue session/prompt while a turn is running instead of rejecting it with -32603
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 54/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- typescript
調査の方向性
Start by tracing the mcode acp handler for session/prompt and the existing TUI and ACP queue paths; inspect the queue extension methods and their tests. Reproduce a prompt arriving during an active turn, then verify the selected behavior: the message is delivered once after the turn and its response tracks that queued turn, or the error names the callable queue method. Check that queued messages remain visible through mcode/session/queue/list and removable with mcode/session/queue/delete.
索引モデルが issue の本文から書いたものです。
説明
Product or interface
CLI - ACP
Use case and problem
A third-party ACP client that talks to mcode acp cannot steer a running turn. When it sends session/prompt while a turn is still active, the ACP adapter rejects it:
Internal error: MiniMax Code Runtime failed: Session already has an active Turn. Use queue send to deliver the message after it.
This happens in practice whenever a background message has to reach a session that is busy — for example a parent agent that is notified that its subagent finished while the parent's own turn is still running. The message is not queued and not delivered: it fails.
The agent already has the machinery for this. The TUI queues messages typed during a run, and the ACP adapter exposes the same capability as a vendor extension:
"_meta": { "minimax-code/extensions": { "methods": [
"mcode/session/steer",
"mcode/session/queue/list", "mcode/session/queue/enqueue",
"mcode/session/queue/update", "mcode/session/queue/delete", "mcode/session/queue/steer"
] } }
But the error message only says "Use queue send" without naming the method, and the ACP protocol has no standard way to advertise steering or queueing — the promptCapabilities object in the ACP schema only carries image, audio and embeddedContext, so initialize cannot tell a generic client that steering exists. A generic client therefore has to read the vendor _meta block and guess the method name, and most clients do not.
Desired behavior
Either of these would make mcode acp usable from generic ACP clients:
session/promptreceived while a turn is running is queued and delivered once the running turn finishes, with thesession/promptresponse returned when the queued turn actually runs — the same behaviour the TUI already has. This is the interoperable option, since a client that cannot know about a vendor extension cannot use it.- The error names the exact method to call, e.g.
Session already has an active Turn. Call mcode/session/queue/enqueue to deliver the message after it.— at minimum, the error should carry the method name so a client can recover without reading the source.
Acceptance criteria:
- A
session/promptthat arrives during a running turn is either queued or rejected with an error that names the callable extension method. It is never silently dropped. - With option 1, the message is delivered exactly once, after the running turn, and the
session/promptresponse corresponds to the queued turn. - Queued messages are visible through
mcode/session/queue/listand can be removed withmcode/session/queue/delete, consistent with the existing extension contract.
Platform
Multiple platforms
Alternatives and additional context
- Steering via
mcode/session/steerworks for clients that read the vendor extension, but the ACP schema itself has no capability to advertise it, so clients have to hard-code provider-specific knowledge. - The client side of this problem is tracked in the Paseo repository: https://github.com/getpaseo/paseo/issues/8300 and https://github.com/getpaseo/paseo/discussions/8301 — they are looking at queuing messages on the client side, but a client-side queue cannot be applied when the client is not the one that owns the turn.
- Related open issues in this repository: #295 (parallel queued tasks in the interactive TUI), #335 (separating mid-run steer/queue messages in Goal mode). This request is about the ACP surface specifically, not the TUI.
- 主要言語
- TypeScript
- スター
- 2.1k
- フォーク
- 271
- 平均マージ
- 14時間 23分
- マージ済み PR(30日)
- 35
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
MiniMax-AI/minimax-code のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
MiniMax-AI/minimax-code#556 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
MiniMax-AI/minimax-code#507 ·
メンテナーはふだん 1 日以内に返信
-
bug needs-triage tui
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
MiniMax-AI/minimax-code#481 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug cli documentation needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
MiniMax-AI/minimax-code#299 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
desktop
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
MiniMax-AI/minimax-code#565 ·
メンテナーはふだん 1 日以内に返信
MiniMax-AI/minimax-code の issue をすべて見る
似ている issue
-
Replace discontinued crypto-js in the theme対応中かも @aelmanaa が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
PaloAltoNetworks/docusaurus-openapi-docs#1689 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
solana-foundation/solana-web3.js#4015 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
documentation
難易度 1/5 1〜3時間 初心者へのやさしさ 90/100
ivopogace/opencode-courier#422 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
chapel-lang/chapel-vscode#158 ·
メンテナーはふだん 1 日以内に返信