Files
pipelines/docs/notes/chat-automations-metadata.md
T

25 lines
1.5 KiB
Markdown

# Chat scheduled-work metadata
The read-only `chat_automations` websocket command exposes provider-owned
scheduled work for one operator chat. It deliberately distinguishes a
supported empty result (`active_count: 0`) from an unavailable provider
(`active_count` omitted), so a composer must not render unknown as zero.
OpenCode endpoints that expose scheduling use the documented experimental read endpoint and filters
the validated response to the requested session and `active` status. Fresh
Claude CLI processes now register a private native Stop-hook observer; only a
validated bounded `session_crons` snapshot is promoted, with `observed_at_ms`
identifying when it was reported. Old hosts and sessions without that snapshot
remain unavailable. Codex has no documented native scheduled-management read
API. No schedule is created, changed, resumed, or inferred from a transcript or cwd.
Pipeline291 passed implementation and code review (UI review skipped: backend-only),
then blocked at its read-only delivery-stage commit step. The manager retained the
candidate, updated existing API pipeline22 to v10 so its local commit stage can
write, and took over integration/landing. This metadata task alone is not the
composer feature and has not been deployed. Current installed OpenCode2.0.32
appears not to expose the newer experimental API; unavailable is intentional.
Manager integration: go build ./..., go vet ./..., go test ./... all passed;
full test log /tmp/chat-automation-go-integration.log. No service restart.