The agent's week is a file, and the file starts where last week's stopped

Friday, 17:00. A cron entry in the agent's container runs one GET.

/agent/logs/export?source=tool&status=error&since_seq={last}&format=jsonl: every tool call that ended in error since the cursor the previous Friday saved. curl -o puts it at reviews/2026-W36.jsonl on the container's disk; next week's cursor goes into a KV key. Nothing is exported twice.

The engineering manager reads it Monday like a report: which tools failed, in which session, how often. session_id= narrows it to one run. The stream endpoint rides the same seq, so a dashboard can tail live while the export catches up in batches from the same numbers.

No log shipper, no SDK hook, no observability seat per bot. The agent's log is a URL that hands itself out in the shape you asked for.

The agent's week is a file, and the file starts where last week's stopped.