Sessions, live feed and activity
Watch requests as they finish, see who is online, and open your team's agent sessions in the console, whether remote, shared, captured from the request log, handed off or shared live.
Three console areas show what is happening now and what agent sessions did:
| Page | Shows | Needs |
|---|---|---|
Live (/live) |
requests as they finish, newest on top | logs:read |
Activity (/activity) |
daemons by heartbeat, people using the console, recent changes | daemons:read (every role but billing) |
Sessions (/sessions and below) |
remote, shared, captured, handed-off and live-shared agent sessions, and session history | logs:read (owner, admin, developer, viewer) |
Live request feed: /live
Open Live to watch requests finish. Each row has the model asked for and the one served, the gear and role (x-venom-gear, x-venom-role), the key and its member, status and error, where it ran (cloud, daemon or public mesh, and which daemon or provider), latency, time to first token, tokens and cost. A row opens its trace at /requests/{id} (see Requests). A strip on top shows requests per second, spend per minute and a sparkline of the last 30 minutes' spend.
The filter box takes a log query without pipes, time terms or content terms, for example:
key:ci-* is:errorThe status pills write is:ok, is:error, is:partial, has:filter or is:background, and the cost floor writes cost:>=$x. Keys: p pauses or resumes, / focuses the filter.
How it updates: the page polls every 2 s while rows come, slows to every 10 s while none do, backs off up to 30 s on errors, and stops while the tab is hidden or the feed is paused. Resuming catches up with no rows lost or doubled. The first page holds the last hour; each poll lists at most 100 rows and counts the rest.
Owners, admins and the operator see every request in scope. Developers and viewers see only requests sent with their own keys.
| Error | Cause |
|---|---|
"This filter can't run live" (live_pipeline, live_window, live_content) |
The filter has a pipe, a time term or a content term. Use Requests for those. |
| "The feed stopped" | The poll failed; it retries on its own, doubling the wait. |
Activity: /activity
Who is online right now. Three cards, refreshed every 15 s while the page is open and visible:
- Daemons: each with a presence dot from its heartbeats (live, suspect, offline), the last heartbeat, a link to its page and to its requests in the explorer.
- People: console users seen in the last 5 minutes.
- Recent activity: the newest audit log entries (sign-ins, keys, daemons, settings changes). Only for roles with
audit:read(owner, admin, developer).
Remote sessions: /sessions
venom serve sessions that clients opened through this cloud, each pinned to the daemon that runs it. Pills filter by state: Live (the default), Closed, All. Columns: session, state (live, daemon lost, closed), the daemon it is pinned to, key, started, last event, request count. Each links to its daemon and to its requests.
The header links every other session view: Live, Handoffs (with a count of those waiting for you), History, Shared sessions, Captured sessions, Daemons.
A daemon serves remote sessions when it lists serve under its capabilities on the daemon page. If this cloud has no remote session API, the page says "Remote sessions aren't served here yet".
Shared sessions: /sessions/shared and /sessions/{id}
Sessions people uploaded from the CLI with /share or venom session share (see Share and redacted copies). The CLI redacts on the laptop before upload and asks first. The list searches titles, session ids and models, newest first, with each share's expiry.
/sessions/{id} opens one share's transcript: steps with search, a replay slider, the cumulative cost and time chart, subagents nested under the tool call that ran them, image thumbnails, and comments on a step or the whole session. ?step= opens on a step. Every open writes a session_share.viewed audit row. When the CLI signed the session's actions, the page shows the action log's head so you can check it on the machine.
| Control | Who | What |
|---|---|---|
| Comment | anyone who can open it | on a step or on the session (up to 4,000 characters) |
| Access | org:manage |
"Everyone in the org who reads logs" or "Admins only" |
| Public link | org:manage, when the org allows public links |
a link for N days (up to the org's longest); shown once; revoke any time |
| Delete | org:manage |
removes the share and its comments |
/sessions/{id}/network is the share's network map: every host the session contacted, from where, how often and what was refused, with hosts outside the allow list or new for the repository flagged (see Shared sessions in egress). Shares made before the CLI kept a map show "No network map"; share again to add it.
/sessions/{id}/replay opens the share in the replay debugger, with the session's request log rows laid over its turns (billed cost, gear, status, filter hits). ?turn= opens on a turn (1-based). Only the first 2,000 requests are joined.
Sharing settings
Under the shared list, for org:manage; changes are audited as session_sharing.settings and can be undone from the audit log.
| Setting | Default | Range |
|---|---|---|
| Public links | off | on or off |
| Keep shared sessions for (days) | 30 | 1 to 365; then deleted with their comments |
| Longest public link (days) | 7 | 1 to 30 |
Uploads are stored sealed. A deployment without VENOM_VAULT_KEYS answers uploads with 503, and the page says "Sharing needs the vault". A share is at most 4 MB.
Replay debugger
Both /sessions/{id}/replay and /sessions/captured/{session} use it: the figures (cost, tokens in, cached and out, wall time, errors), a lanes chart (the main session and each subagent on its own row, a block per model call), cost per turn beside the cumulative cost, the timeline of turns, and the selected turn in full: model and route, tool calls with arguments and results, subagents and their cost, filter, redaction and fallback markers, and the request log rows it was joined to.
| Key | Does |
|---|---|
j or → / k or ← |
next / previous turn |
space |
play or pause |
$ |
the most expensive turn |
e / E |
next / previous error |
g / G |
first / last turn |
? |
the key list |
Captured sessions: /sessions/captured
Sessions as the request log saw them, without anyone sharing them: every request that carried a session id, grouped by its root session, with subagents and side requests under their parent. Pick a window (24 h, 7 days (default), 30 days) and search. /sessions/captured/{session} replays one from the log alone. The log keeps metadata, so prompts, answers and tool calls are not shown; open a request's row for its stored content (needs content:read, audited). If someone shared the session, the page links the full trace. At most 2,000 requests per session are shown.
Handoffs: /sessions/handoffs
Sessions handed from one teammate to another with /handoff @alice or /handoff team:<name> in venom (see venom handoff).
| Box | Shows |
|---|---|
| Inbox (default) | open handoffs to you or to a key group you hold a key of |
| Sent | yours |
| All | the org's; only for org:manage |
/sessions/handoffs/{id} shows the sender's note (goal, next step, what is done, plan, open questions), their message, the branch with its diff stats, the shared transcript, and the command that picks it up. Accepting runs on the recipient's machine with venom handoff accept, in a checkout of the repository. In the console a recipient can Decline (with a reason the sender sees) and the sender can Cancel (it leaves the inbox; the transcript stays).
Session history: /sessions/history
A short summary of every member's venom session (goal, outcome, decisions, files touched, cost, who ran it where), searchable across the org. venom uploads summaries only after an admin turns collection on here.
| Setting | Default | Who |
|---|---|---|
| Collect session summaries | off | org:manage; audited as session_summaries.settings |
| Keep summaries for | 90 days (1 to 730) | org:manage |
The operator picks an org in the org switcher first.
Live sessions: /sessions/live
Sessions teammates are sharing as they run (/share live in venom), that you may watch, newest first. /sessions/live/{id} is the viewer: the transcript as it grows, the permission prompt that is waiting, and who is watching. Joining writes a live_session.joined audit row once.
The session's owner grants roles from the terminal (/share live grant <member> drive) or, as owner or org:manage, in the viewer:
| Role | Can |
|---|---|
| Watch | read along |
| Co-drive | also send prompts from the composer |
| Co-drive + approve | also answer the session's permission prompts |
| Blocked | nothing |
The owner (or org:manage) also gets Stop sharing.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| No remote sessions | No daemon reports serve, or no client opened a session through this cloud. |
| "No shared sessions yet" | Nobody ran /share or venom session share against this cloud. |
| Uploads fail with 503 | The deployment has no VENOM_VAULT_KEYS. |
| Session history stays empty | Collection is off (the default); turn it on, then members' next sessions upload. Claude Code sessions need the plugin. |
| Captured session has no prompts | The request log keeps metadata only; open a request for its stored content. |
Related
- Requests and request traces
- Log query language
- Failures: why sessions failed, with example sessions.
- Claude Code sessions in Venom: send Claude Code sessions to History and Notes.
- CLI sessions: share, resume and summaries from the terminal.