New Analytics Views, Chat-Level Reporting, and a Refreshed Interface

Reporting has a view for each thing you might ask about — workflows, chats, users, and models — and it now answers questions down to the individual chat. The controls you click all day share one refreshed design.

Reporting

• Views for workflows, chats, users, and models: Reports has a view for each, so consumption can be read against the thing you are asking about rather than one combined total.

• Workflow detail: Open a single workflow from the list and see its own report.

• Chat-level reporting: Reporting answers questions down to the individual chat, including its name, its message count, and whether it has been deleted.

• Budget snapshots in reports: Reports read budget snapshots, so spend can be read against a cap over time rather than only where it stands now.

• Names instead of user IDs: Top users and the Workflows view show reporting user names, and fall back to the email address where a name is missing.

• Only attributed usage in the Workflows view: Usage that cannot be attributed is dropped from the view, so the totals reconcile.

• More complete report data: Workflow reports return property types, reporting dimensions capture them, and chat rows carry their workspace so multi-workspace analytics separate correctly.

• Filter and count fixes: Metrics stay visible when you change the selected period, facet counts are exact across the full scope, measure filters resolve against the merged activity, and the month in the token report date picker is no longer off by one.

• Reporting access on your profile: Your profile shows the organization reporting access you have.

Interface

• One design pass across the controls: Switches, checkboxes, radio buttons, toggles, badges, tabs, and breadcrumbs share one visual treatment, and the workspace selector has been reworked with them.

• Keyboard and screen reader fixes: Menus are navigable by keyboard and announced correctly, and nested menu behaviour works again.

• The model is named: The Go Agent V2 settings tooltip names the model actually in use.

• Steadier rendering: Workflows render without the flicker on load, dates and times are handled the same way throughout, and action bars match the current design.

Reliability and speed

• Faster on wide projects: Adding an entity to a project carrying many properties is substantially faster.

• Transient database errors retry: The tool runner retries a transient database error rather than failing the field.

• Faster startup: Behaviours load without pulling in every module, which cuts startup time and memory.

• MCP routing scoped per message: Connector routing is enforced per message, preventing one connector interfering with another.