Admin Recent Activity

ONE page of the newest sessions across EVERY customer workspace.

THE READ THE ADMIN CONSOLE ACTUALLY MAKES. /v2/api/activity wants "what just happened anywhere", and every list route below it is scoped to one team. It once fanned out /sessions + /runs per team (80 concurrent requests at 40 workspaces, 24.9s, 2026-08-27); then it asked for a per-team sample in two statements, which kept the round trips flat but let the ANSWER grow with the estate — 125 workspaces answered 2.2MB in 1.2–3.5s for a screen that draws 30 rows (2026-09-05). Owner: "we have way too much activity … cut it … limit … pagination and fast".

So this is a page: limit newest sessions across the whole estate, ranked by their newest run, from offset; has_more says whether another page follows. runs holds exactly one run per session — the newest — with parent_session_id / root_session_id already resolved, and each session's metadata is cut to the two keys the console reads.

sessions_per_team / runs_per_team are still accepted so a caller built against the sampled shape keeps answering, but they are NO-OPS: they described the per-team budget this replaced, and honouring them would put the growth back.

Authorisation is list_customer_teams' own — the local-operator gate — and the team list it returns is the exact scope of the read, so this can never reach a workspace the caller could not already list. The full team list rides along (~26KB at 125 teams) because the console names every row by it.