Runtime timelines
See related agent actions as one execution.
Runtime sessions group individual tool-call logs into one timeline for an agent execution across GitHub and database tools. The detailed action evidence remains inspectable, including policy decision, mode, outcome, and connector metadata.
Correlation model
MCP clients may send an explicit session id with x-zg-session-id . The CLI bridge now propagates one per bridge process. When no explicit id exists, z-gateway creates a bounded implicit session by workspace, agent, and environment.
What appears in a session
A single session can include repository reads, issue or pull request work, schema inspection, read queries, write proposals, approvals, and blocked decisions. Runtime logs still hold the detailed evidence for each action; sessions make the overall agent execution easier to scan.
Legacy logs
Historical logs are not backfilled into artificial sessions. They remain visible as legacy ungrouped actions in the runtime logs view.