Agents read your product analytics and session recordings
Every production site already counted its visits and recorded a sample of them, but an agent could not reach any of it. Now it can: get_analytics answers about twenty reports, from an overview against last week to pages, query strings, campaigns, custom events, journeys and retention, and get_analytics_funnel shows which step of a flow people abandon. These are aggregates and come with read access.
With visitors:read, which you approve like other customer data, an agent lists the sessions behind a drop-off and reads their recordings. A recording comes back as a timeline of pages, clicks and inputs, never as video and never with page text or what anyone typed, with signals where a visitor seemed stuck: repeated clicks, a click that did nothing, a switch flipped back and forth, a form left half-filled.
Credentials in URLs, such as password-reset tokens and sign-in codes, are now redacted in the browser before a visit is sent, and in everything an agent reads. Production deployments and approved broadcasts appear as notes on the charts, so "did the fix help?" has an answer there. See Product analytics in the docs.