Agent Analytics

Agent analytics explains how agent-assisted work is attributed in Insights and roadmap reporting. Runtime state lives in Agent Sessions.

What counts in Insights

Insights does not count completed agent sessions as completed work. The work item carries the reporting signal.

The underlying work needs agent attribution. Without that taxonomy signal, the session can still be visible in Agent Sessions, but it will not explain agent involvement in reporting.

When a worker claims work linked to a child item, agent attribution is added to that item and its parent initiatives. That lets roadmap filters and Insights show agent involvement before every descendant item is complete.

Where to look

Use Taxonomy Analytics for taxonomy distribution, including coding tools. Use Agent Sessions for runtime status: queued, claimed, active, completed, failed, released, or cancelled.

Use Roadmap Progress when you need to see whether agent-assisted work is tied back to planned initiatives.

Keep attribution clean

Agent analytics depends on Taxonomy and session records from Agent Sessions. Keep agent work linked to initiatives, bugs, or completed tasks so reporting tells the same story as delivery.