agent-team-event-log

Inspect append-only event histories by applying filters like run, entity-type, and event type to isolate relevant events for debugging. This retrieves ordered state events from the agent-team event store via CLI, allowing you to diagnose exactly why a run progressed to a specific state.

Yes, you can filter the event log by run, entity-type, entity, event type, and after-version for incremental polling. This allows you to retrieve ordered data slices from the event history, ensuring you only process new or updated state events during downstream analysis.

Auditing state events across runs is done by querying the append-only event store via CLI with specific filters. You can isolate and view ordered event histories by run and entity, providing an accurate chronological record for compliance audits and issue reproduction.

An agent-team run progresses to a specific state based on associated task and message events. You can reproduce and diagnose the issue by examining the ordered event history with filters, isolating the exact state version and event type that triggered the transition.

No, the event log inspection tool does not require external dependencies. It operates directly against the agent-team event store via the CLI, allowing you to apply filters and output ordered data immediately for downstream analysis and auditing.

Use event version filtering with after-version for incremental polling to retrieve only recent state changes. Use run filtering when you need to view the complete ordered event history for a specific execution to diagnose overall progression or audit the full lifecycle.