feat(coding-agent): report prompt disposition in RPC responses

Successful RPC prompt, steer, and follow_up responses include
data.disposition ("handled", "queued", or "started" for prompt), so clients
know whether to wait for agent_settled.

fixes #9098
This commit is contained in:
David Brailovsky 2026-09-25 14:51:52 +02:00
parent b3487650f6
commit e473b5cd8b
11 changed files with 335 additions and 188 deletions

View file

@ -65,7 +65,7 @@ After a runtime replacement, subscriptions belong to the old `AgentSession` and
A prompt sent while the session is already streaming must specify whether it should steer the current run or follow it. Calling `prompt()` without that choice rejects rather than guessing.
A steering message enters after the current assistant turn and its tool calls. A follow-up enters after the current run finishes its pending work. `steer()` and `followUp()` expose those behaviors directly.
A steering message enters after the current assistant turn and its tool calls. A follow-up enters after the current run finishes its pending work. `steer()` and `followUp()` expose those behaviors directly and return `"queued"` if the input was queued (including after an extension transformed it), or `"handled"` if an extension consumed it.
`abort()` stops the active operation and waits for the session to become idle. `waitForIdle()` waits without aborting it.