Sessions
List live and historical sessions for your org from the CLI
A session is uRun's core primitive — a live, bidirectional connection between a
browser client and a function running on GPUs (see the
session model). urun session list shows the sessions your org has
created, live and historical.
List sessions
urun session listAPP FUNCTION STATE CREATED
krea-realtime krea_runtime closed 2026-06-15 09:01:12
hello-h100 hello connected 2026-06-15 09:14:55Two separate facts about ordering, so they never seem to contradict:
- Fetch order is newest-first —
--limit Nreturns the N most recent sessions. - Print order is newest-last — within that page the table is printed oldest→newest, so
the most recent run is the last line and the command stays friendly to
tail.
Add --json for raw output (newest-first, unmodified).
Filter and limit
urun session list --limit 25
urun session list --state connected| Flag | Default | Effect |
|---|---|---|
--limit N | 100 | Max sessions to fetch (newest-first) |
--state STATE | (all) | Filter to one backend state |
--json | off | Raw JSON instead of a table |
Backend states
--state filters on the backend session state:
| State | Meaning |
|---|---|
allocated | A session slot has been allocated, not yet connected |
connected | The client is connected and streaming |
closed | The session ended cleanly |
failed | The session failed during allocation or transport |
cancelled | The session was cancelled |
These are the backend session states reported by the control plane. They are distinct
from the client-facing lifecycle phases the browser SDK surfaces — the full nine are
idle, queued, unavailable, provisioning, connecting, live, error, ended,
and expired — see the session lifecycle.
For deep per-session inspection (events, control docs, streams) use the console's
Sessions surface.
Example: tail the latest failures
urun session list --state failed --limit 10Next
- Compute — what GPU capacity is provisioned right now.
- Sessions in the console — drill into a single session.