Skip to main content
Analytics shows what your organization’s agents did over a time window: how many agent session hours they used, how their sessions completed, and how their sandboxes started. Use it to find the agent behind a change in usage. Each agent’s Observability tab tells the story for that one agent, with its errors and speed.
Any organization role that can read sessions can open Analytics: user, developer, or admin. The figures cover the organization you are working in. See Organizations and roles. Analytics is a console screen; it has no API-key operation. What your agents cost is on the Billing screen; see Billing.

​
Open Analytics

Pick a view and a time window. The page opens on Usage for the Last 7 days.
  1. In the Recursion console, click Analytics in the sidebar.
  2. Choose a view: Usage, Completions, or Environments.
  3. Choose a window: Last 24 hours, Last 7 days, Last 30 days, Last 90 days, or Last year.
Next to the window, a pill says how current the figures are: Up to date, or Behind by some minutes or hours. Figures are updated as work is recorded and normally trail it by a minute or two, so a session that just finished can take that long to appear.

​
Read usage

Usage shows one figure: Agent session hours, the time your agents’ sandboxes ran in the window. It is the time metered for billing: each sandbox run counts from start to stop, idle time included, once the run is charged. A run is charged when its sandbox stops, so a session that is still running isn’t counted yet. Environment setup isn’t included. Below it, Agent session hours by agent charts the window by day or by hour, stacked by agent. Hover a column to see that period’s hours for each agent. Periods are in UTC. The Agent table lists each agent’s session hours.

​
Narrow to an agent

Click an agent in the Agent table, or in the chart’s legend, to filter the whole page to it. The filter appears above the figures. Click it to remove it, or click Clear all.

​
Read completions and environment startup

  • Completions shows how many root sessions completed, how many complete per hour or per day, and how long they took from creation to completion, including time spent waiting. Active agents lists the same for each agent.
  • Environments shows how many sandboxes started, how many failed to start, and how long startup took, by provider, compute, machine type, and environment.

​
Follow one agent

Open an agent from Agents and choose Observability. It shows the agent’s sessions, tool error rate, and agent session hours; activity stacked by agent version, as Sessions, Errors, or Session hours, so you can see whether a new version changed anything; per-session means and durations; and its tools by use. The agent’s Sessions view shows its completion figures above the list.

​
What can go wrong

  • A session you just ran isn’t counted yet. Check the freshness pill; figures trail work by a minute or two. Session hours count once the session’s sandbox stops and its run is charged.
  • Agent session hours say they’re still being calculated. Hours for earlier work are being worked out. This takes a few minutes; the other figures are already complete.
  • You’re looking for cost. Analytics shows usage, not spend. Read what your tenant spent on the Billing screen, or one session’s cost in Usage and cost.
  • Percentiles look rough. Durations such as an agent’s Tool call latency are approximate. Each says how many measurements it’s based on.

​
Next steps

Sessions

Launch work and read the sessions behind these figures.

Billing

Track what your tenant spends and buy credits.