agent-team-ops

You can inspect agent-team runs using operational commands that query current state and summaries without running agents. These commands provide read-only access to active run status, message history, and event logs for auditing purposes.

Viewing event logs and message history is done through run-scoped inspection commands that retrieve append-only event records and scoped messages. This provides full traceability of agent-team operations and communication sequences for a specific run.

Yes, you can export the machine-readable CLI contract for tooling and integration. Schema export generates a machine-readable contract defining the operational command surface, enabling external systems to integrate with the agent-team interface.

Run hygiene involves inspecting operational state and closing completed runs to maintain a clean execution environment. You need to finalize runs when auditing current state and ensuring finished agent-team sessions do not linger open unnecessarily.

No external dependencies or components are required to perform state inspection on agent-team runs. The operational commands are self-contained and implement the required command surface per SKILL.md prerequisites without additional installations.