Vercel
The Sessions view in Vercel’s AI Gateway logs groups individual requests into complete sessions. It shows how session affinity routed each request, alongside the models, providers and costs involved across the conversation.
According to the Vercel changelog, each row identifies the coding agent or app that ran the session. Examples include Claude Code, Codex and Cursor.
What Vercel’s Sessions view shows
The new grouping replaces a request-by-request inspection with a session-level record. Builders can see which services handled a conversation and how much of the input was cached across every turn.
| Session field | What it shows |
|---|---|
| Agent or app | The coding agent or application that ran the session |
| Routing | How session affinity routed each request |
| Models and providers | The models used and the providers that served them |
| Cost | Spend attached to the session |
| Cached input | How much input was cached across the session’s turns |
The logs also expose the session ID, number of turns and cache hit rate. These fields connect routing behaviour with the resulting cost and cache usage, without splitting one conversation across separate request rows.
Following one AI session from agent to provider
A session may include several turns and requests. The Sessions view keeps those requests together while showing the agent that started the work, the models and providers used, and the associated spend.
This creates one place to inspect whether session affinity kept requests on the expected route. The cache figures show how much input was reused throughout the same conversation. Teams can compare sessions from different agents or apps using the same set of fields.
The release joins the wider set of changes covered in What Vercel Shipped Across AI Gateway in Mid-October.
Vercel published the Sessions view update on 17 October 2026. It is available through the AI Gateway logs dashboard.
Frequently asked questions
What is Vercel Sessions view?
Sessions view is an AI Gateway logs view that groups related requests into sessions. Each row shows the agent or app, routing, cost, models, providers and cached input for that session.
What information does Sessions view include?
It includes the session ID, coding agent or app, cost, models, providers, turns and cache information. It also shows how session affinity routed each request.
Which Vercel plan includes Sessions view?
The changelog does not specify plan or pricing requirements. It links users directly to the Sessions view in the AI Gateway logs dashboard.
Sources
3 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.
Supabase
Jotform
Gemini