-
Notifications
You must be signed in to change notification settings - Fork 76
Analytics dashboard undercounts agents that primarily produce single-turn sessions #256
Description
The analytics dashboard applies the "exclude single-turn" filter by default, but nothing on the dashboard indicates this. The Agent Comparison panel showed 1 copilot session for me — the actual number in the database is 332.
It took some digging to realize the single-turn filter was responsible. The filter toggle is in the sidebar under "Session Type", but the dashboard panels don't hint that results are filtered.
Two things that would help:
-
Some indication on the analytics dashboard when the single-turn filter is active. A user looking at the numbers today has no way to know sessions are being excluded without already knowing about the filter.
-
Almost all my Copilot sessions are roborev reviews, which are single-turn by nature. Today there is no way to distinguish them from other single-turn sessions — the
session.startevent just hasproducer: "copilot-agent"with no roborev-specific metadata. It would be nice if roborev sessions could eventually be identified and filtered independently.
Related: #57
Environment
- agentsview v0.17.1
- 332 Copilot CLI sessions, 331 with
user_message_count = 1 - Windows 11