Events and observability

Consume the full event stream when running an agent. A provider response, tool result or visible answer is part of a longer execution record; the terminal session outcome determines whether the runtime completed, failed or interrupted the work.

Follow one session

Use the dashboard or cayu session --help to inspect recorded messages and events. Retain session, interaction, step and operation identities when relating events to domain receipts. Avoid using incidental log ordering as the only proof of a transaction.

Keep three views separate: the durable execution history, the context projected to a model, and the provider’s request/response format. A compacted context does not imply the stored trajectory was deleted.

Diagnose failures

Start with the terminal failure and owning subsystem. Then inspect provider diagnostics, tool policy, environment lifecycle or storage evidence. A cancelled local task does not prove an external operation stopped. A failed observer does not automatically mean the candidate’s domain operation failed.

Use diagnostics for structured support workflows and diagnostics CLI for release-matched flags. Review retained data before sharing a diagnostic bundle; your application’s prompts, attachments and tool results may contain sensitive information.

Reference: events, observability and runtime guarantees.