Sessions
A session is a continuous period of AI activity from a single identity — typically one Claude Code or Cursor workspace. Sessions give you a per-task view of cost, tool calls, and governance decisions.
What is a session
Sessions are created automatically when a developer or agent begins sending requests through the proxy. A session is marked expired once it has been idle longer than the configurable idle window (session_idle_window_minutes, default 60 minutes — set to 0 to disable idle expiry) or when the developer explicitly disconnects. Independently of the idle window, every session also has a hard expiry — 8 hours after it was created (refreshed if the same conversation continues past it) — after which it is permanently closed. If a developer resumes an idle-expired session before its hard expiry, it automatically revives rather than starting a new session.
Each session captures:
- The identity (developer email or agent ID) and the tool they were using
- A declared purpose — optionally set by the developer or inferred from the first request
- Total token usage, estimated cost, and model mix for the session
- Every tool call and LLM request made during the session, with governance decisions
Session list
Navigate to Identity → Sessions to see all sessions, filterable by developer, status (active, ended, expired, budget exceeded, paused), and purpose. An admin can pause or resume an active session from the list without affecting the developer's connection.
Session detail
Click any session to open the detail panel. It shows:
- Summary — AI-generated description of what the session accomplished, which tools were used, and key outcomes
- Cost breakdown — input tokens, output tokens, cache hits, and estimated cost by model
- Governance timeline — every allow, deny, warn, and approval decision in chronological order
- Tool calls — the full list of MCP tool calls with arguments and outcomes
The detail panel shows both Start (when the session was first created) and Last turn (the timestamp of its most recent activity); the session list is sorted by Last turn so the most recently active sessions surface first.
Session budgets
Sessions inherit the default session cap set in Settings → Budgets → Limits. When a session hits its cap, further requests are blocked until the session ends or an admin resets the budget from the session detail panel.
Individual developers can request a higher cap for a specific session by setting it in their PAT. Admins can override any session cap from the detail panel.