Skip to main content
The Sessions page is a searchable, sortable table of every agent session Claw Lens has recorded. You can filter by agent, time range, and session type, then click any row to expand a full detail panel for that session.
Session data is read from the OpenClaw agent session files stored under ~/.openclaw/agents/{agent}/sessions/.

KPI strip

The five KPIs at the top of the page summarize the currently visible session set:
MetricDescription
Total sessionsNumber of sessions matching the current filters
Active nowSessions with a message in the last 10 minutes
Errors todaySessions started today that contain at least one error message
Errors 7dError-containing sessions in the last 7 days
Errors 30dError-containing sessions in the last 30 days
Error counts are shown in red when non-zero.

Filtering and sorting

Use the controls above the table to narrow down the session list:
1

Search by session ID

Type any part of a session UUID into the search box. This filter bypasses all other filters and matches across all loaded sessions.
2

Filter by agent

Select an agent from the dropdown to show only sessions for that agent.
3

Filter by time range

Choose Today, Last 7 days, Last 30 days, or All time. When a time filter is active, token counts and costs are recalculated to include only messages within that window.
4

Filter by session type

Choose All sessions, Cron only, or Non-cron to isolate scheduled vs. interactive sessions.
5

Sort

Sort by Newest (last activity), Tokens, Cost, Errors, or Cache hit (ascending).
Click Clear to reset all filters at once.

Sessions table

Session Table 1
Each row in the table represents one session. The columns are:
ColumnDescription
SessionFirst 12 characters of the session UUID, in blue monospace
AgentName of the OpenClaw agent
Live statusrunning (message in last 30 min) or idle
ModelPrimary model used in the session
TokensTotal tokens across all messages
CostTotal cost for the session
Cache hitcache_read / (cache_read + input_tokens) — colored green ≥ 80 %, amber ≥ 50 %, red below 50 %
Context pressureHow full the context window was in the last assistant message: healthy (0–69 %), warning (70–89 %), critical (≥ 90 %)
Burn rateDirection of context growth across the last 3 messages: rising (red), stable (amber), cooling (green)
Last signalThe last stop_reason from the final assistant message
ErrorsNumber of error messages in the session; shown in red when non-zero
DurationWall-clock time from session start to last message
Avg per msgAverage tokens per assistant message
Last activeTimestamp of the most recent message
StartedSession start timestamp

Last signal values

SignalMeaning
Normalstop or end_turn — session completed normally
Errorerror — the agent encountered an unrecoverable error
Abortedaborted — the run was cancelled
Max tokensmax_tokens — the context window was exhausted
Activetool_use — the agent is mid-turn, waiting for a tool result

Cron vs manual sessions

Session Cron 1
Sessions triggered by a cron schedule are automatically tagged. You can distinguish them using:
  • The Cron only filter in the filter bar
  • The Cron field in the detail panel, which shows the cron task name when applicable
Scheduled sessions appear in the Cron Jobs panel on the Overview page and in the Token Usage cron vs manual breakdown.

Session detail panel

Click any row to expand an inline detail panel for that session. The panel has two tabs.
Session Details

Overview tab

The Overview tab is divided into three columns: Column 1 — Session stats
  • Agent name, duration, start time, last updated
  • Message count, error count, total cost, total tokens
  • Whether the session is a cron session (and which cron task, if applicable)
Column 2 — Cache breakdown A horizontal bar showing the proportion of token types: input (blue), cache read (green), cache write (purple). Below the bar:
  • Cache hit rate as a large percentage (green ≥ 80 %, amber ≥ 50 %, red below 50 %)
  • Exact token counts for each type
Column 3 — Models and tools
  • Per-model message count and cost
  • Per-tool call count and average duration
Charts Below the three-column section, three stacked charts provide a per-step view of the session:

Cost per step

A bar chart of cost per assistant message, ordered by sequence number. Useful for spotting expensive individual turns.

Tokens per step

A bar chart of total tokens per assistant message. Rising bars indicate the context window is filling up.

Context pressure

A line chart of context window usage over time, with reference lines at 70 % (amber) and 100 % (red). Error steps are marked with red dots.

Messages tab

Session Messages
The Messages tab lists every message in the session in a table with:
  • Sequence number, model, role
  • Input, output, cache read, cache write, and total tokens
  • Cost per message
  • Error flag and error message
  • Latency (time since previous message)
Click any row to expand the raw message content, including tool call inputs, tool results, and text blocks.
From the detail panel header, click View in Timeline to open the Session Timeline for a full message-by-message visual breakdown of that session.
Sessions Navigate To Timeline
You can also navigate to a specific session directly via URL:
/sessions?q={session_id}
The page will auto-scroll to the matching row and open the detail panel.