Files
pipelines/docs/notes/claude-native-automation-snapshots.md
T

1.3 KiB

Claude native automation snapshots

chat_automations does not start a Claude turn or inspect a transcript. Fresh Claude CLI initialization registers one private Stop hook callback. When the native callback contains the expected main-thread session and a bounded session_crons list, Pipelines retains only its IDs, count, and the report timestamp. One-shot and recurring entries are both counted.

Detachable hosts acknowledge that exact observer callback themselves, including while the Pipelines server is disconnected. The snapshot is independent of the bounded output spool, so reattachment or spool trimming cannot erase it. Missing/malformed metadata clears the snapshot to unknown while the observer still receives its nonblocking acknowledgement. Wrong-session data cannot update a count. Permission callbacks remain operator-owned; other SDK callbacks retain their existing response behavior. Missing data is never an empty schedule.

The API's observed_at_ms describes the last native Stop snapshot; it is not a live schedule query and does not infer work from historical CronCreate calls.

Reported native timers prevent idle cleanup while pending. Empty snapshots permit normal cleanup. The manager completed lifecycle fixes and integration checks after run292; see claude-automation-manager-review.md for exact evidence and limits.