Expose session-owned chat automation metadata

This commit is contained in:
2026-11-08 15:24:23 +00:00
parent cecfa39aac
commit 9d3358be47
12 changed files with 413 additions and 0 deletions
+13
View File
@@ -543,6 +543,19 @@ sessions pipeline runs create. The protocol types are:
server keeps observing it while its tasks run (bounded like an unattended
turn: at most 16 such chats and 6 hours). Once released it reports none
rather than a stale count.
- `chat_automations` reads provider-owned scheduled work for one operator chat.
Its body is `chat_query: {session_id}` and the reply is
`chat_automations: {session_id, provider, status, active_count?, reason?}`.
`status` is `supported` or `unavailable`; a supported empty result has
`active_count: 0`, while an unavailable result omits the count (unknown is
never represented as zero). OpenCode uses its documented
`GET /api/experimental/schedule?sessionID=...` read and counts only records
whose native `sessionID` matches and whose status is `active`. The older
OpenCode serve surface, Claude Code (which currently exposes schedule data
only through events/hooks), and Codex report their exact readback limitation.
The request is ownership-checked against the operator session registry,
bounded and read-only; it never starts or resumes a model turn and does not
inspect transcripts or count project/global work.
- `chat_subscribe` attaches a connection to one session's shared live stream (body
`session_id`) and replays the session's still-pending approval requests, so every
client that watches a session sees every frame any client's turn produces — the