Insights in the dashboard sidebar shows what your agents did over the last 7 days: sessions that finished, how many ended in a merged pull request, time spent, tokens and cost. The server computes the numbers from its own database, and nothing is sent anywhere else.
A session is one agent working on one task in its own sandbox.
What the page shows
The page opens on your active workspace. With two or more workspaces, a selector at the top switches workspace or shows All workspaces. It has two blocks of tiles, each with a daily chart: My statistics counts sessions you own, and Team statistics counts every member's, with each member's color in the chart. Below them:
| Section | What it shows |
|---|---|
| Sessions completed | How many ended, plus how many failed or were abandoned |
| Success rate | Share of finished sessions that merged a pull request or were marked complete |
| Total tokens used | Tokens across all sessions, and the agent that used the most |
| Finished work | Your sessions that ended in the last 7 days, newest first, up to 50 |
| Last 26 weeks | A heatmap of how many sessions were active each day |
| By workspace, By agent | Sessions launched, finished and failed per workspace, and per agent and model |
| Time | Median and slowest session times, working time, waiting time and your response time |
| Usage | Metered cost and tokens |
Days are counted in your browser's time zone, or UTC if the browser reports none. The sections below the tiles cover only your sessions.
Which sessions count
Every session counts on its own, subsessions included. The count of sessions that need you follows the Needs you rule.
A session counts on the day it finished, even if it started before the 7 days. A relaunched session is one session: while it is live again it counts in no finished total, and after it closes again it counts once, on the day of its latest finish, with that outcome.
How a session ended:
| Counted as | Session |
|---|---|
| Completed | completed or merged |
| Failed | failed |
| Abandoned | abandoned or interrupted |
A session you stop yourself is abandoned.
Success rate
A session succeeds when its status is merged, a pull request it opened is merged, or its owner chose Mark complete.
Only pull requests opened through Cloudfield count. A pull request an agent
opens with gh directly is not counted. A merge is counted only after
Cloudfield has seen it. On load, the page checks up to 10 open pull requests
from your finished sessions against GitHub, so a pull request merged after its
session finished appears within a moment. An older one can stay open until its
session's pull request status is read again. If GitHub cannot be read, the row
shows Could not refresh this pull request: <error>.
Time
Time covers sessions that finished in the period.
- Session time: from the latest start (the relaunch, for a relaunched session) to finish. Slowest 10% take over is the 90th percentile.
- Agent working: time the agent spent working, including waiting for other agents, CI or tools.
- Waiting on you: time a session waited for an answer or an approval.
- Your response time: how long sessions waited for you before working again.
A parent session waiting for its subsessions counts as working, not as waiting on you.
Cost
Cost adds up the usage of sessions that finished in the period. These sessions report cost and tokens:
- Claude Code in Background and Enhanced sessions.
- OpenCode and omp in Enhanced sessions, and in Background sessions over ACP.
Every other session, Standard sessions included, is listed as not reporting tokens, and
its cost is unknown, not zero, so cost and token figures are a floor. When some
sessions are unmetered the page says at least $X.
An Enhanced agent reports the running cost of its session. Cloudfield charges
what each report adds, with the tokens of that turn. A restored session, a new
session or Claude Code's /clear neither counts spend twice nor drops it, and
spend the server had not recorded when it stopped counts with the agent's next
report.
If a session moved between accounts after a usage limit, its spend counts under the account that paid. The session's owner decides which person's statistics it appears in.
Cost is reported, not enforced. To cap spend, use a budget. Subscription quota is under Settings → Usage.
System
The System tab shows how busy the server is right now and which sessions use it. The Activity tab is the 7-day history above; System is live.
- Time range. 5m, 15m or 1h scopes the charts. The line beside it reads
Live · every 5s,Paused while this tab is hidden, or the error of the last failed poll; the last data stays on screen, dimmed. - Tiles. CPU busy (user, system, I/O wait and steal), memory used, the data filesystem, network, running sandboxes, and pressure when the kernel reports it. Pressure is the share of the last 10 seconds some task waited for CPU, memory or I/O.
- Resources by session. A donut of CPU or memory use. Each of up to five sandboxes using at least 2% of the host gets a slice; the rest are one Other sessions slice. Everything else is host use outside the listed sandboxes: the Cloudfield server, Docker, host processes and sandboxes you cannot see. Click a slice or its legend entry to filter the ranked list to it; click again or Show all to clear. The list ranks every sandbox by use, with its limit, near limit from 80% of that limit, throttled when CPU is capped, and a 15-minute trend. A session's browser is its own row, with its own limits. A row opens its session, or your own Environment.
- History. CPU, memory, load average, pressure, network and disk I/O.
- Storage. The data filesystem, Cloudfield data by category, Docker storage, container writable layers and, for admins, the largest storage owners.
The server reads host figures from /proc and /sys every 5 seconds and
keeps one hour. Sandbox figures come from Docker's per-container stats, and
from inside each VM with session-runtime vm, and are sampled only while
someone has the System tab open. Admins see every sandbox; members see their
own, and the rest counts toward Everything else. The tab reads This server does not report system stats. Update the server to see them. when the server
is too old.
Limits
- The page covers the last 7 days. Older sessions appear only in the 26-week heatmap.
- Time worked, time waiting and pull requests are recorded only from the day
your server was upgraded to a version that records them. Earlier sessions are
left out of those numbers, and the page says
Aether records this from <date> onwhen only some sessions are measured. - Deleting a session removes it from these statistics.
- The tiles read
This server does not report insights. Update the server to see them.when the server is too old.