Description
Partio should capture structured metrics for each agent session: total duration (wall time from session start to end), number of turns (agent request/response cycles), and model name. These metrics should be stored in checkpoint metadata and exposed via partio explain and the app dashboard. This enables teams to understand AI usage patterns, cost attribution, and session complexity at a per-commit or per-PR level.
Source
Target Repos
Acceptance Criteria
Context Hints
cli/internal/session/
cli/internal/checkpoint/
cli/internal/hooks/
Comment /minion build or add the minion-approved label to begin implementation.
Description
Partio should capture structured metrics for each agent session: total duration (wall time from session start to end), number of turns (agent request/response cycles), and model name. These metrics should be stored in checkpoint metadata and exposed via
partio explainand the app dashboard. This enables teams to understand AI usage patterns, cost attribution, and session complexity at a per-commit or per-PR level.Source
entireio-cliTarget Repos
cliappdocsAcceptance Criteria
partio explaindisplays duration, turn count, and model for each sessionContext Hints
cli/internal/session/cli/internal/checkpoint/cli/internal/hooks/Comment
/minion buildor add theminion-approvedlabel to begin implementation.