What exactly does the array count?
The `totals_by_3rd_party_agent` array carries four fields for each agent: a display name, an identifier that stays stable across reporting periods, the number of jobs the agent app started, and — in enterprise and organization reports only — a session count. Reports are available at enterprise, organization, enterprise-user and organization-user levels, in one-day and twenty-eight-day formats.[1]
The announcement's own caveat deserves attention: the job-count field inside the array counts something different from the top-level field of the same name. Two distinct quantities under one name in the same document create a reading trap for anyone who audits these numbers later. What the number means does not come from its name; it comes from the level it sits at.[1]
What does an empty report prove?
The array counts job starts and sessions; it does not describe what an agent read, what it changed, or which repository it touched. Access is narrow too: enterprise ownership, billing manager status, organization ownership, or a custom role carrying the 'View Copilot Metrics' permission. The people who can see the number and the people who carry the consequences of the agent's work need not be the same.[1]
Then there is the question of how absence looks. When no recognised agent activity exists, the report omits the array entirely. An empty result means nothing was recognised; it does not mean nothing happened. An unrecognised or self-hosted agent never enters this accounting in the first place. What would close the uncertainty is clear: a published, maintained list of which agent apps count as recognised.[1]