Sessions
Governed sessions
Every session a coding agent ran under Threefold: how many calls it made, what it cost, and whether a breaker stopped it. Read from the live service as you look, not a sample.
Sessions
Newest first. Select one to read it from the service.
| Session | Project | Calls | Cost | Tokens | State | Started, UTC |
|---|---|---|---|---|---|---|
| Loading… | ||||||
The listing scans the session table and keeps the newest rows, which is honest at this scale and would not be at any other: a deployment with real traffic wants a secondary index on a recency key instead. The Calls column is cumulative; the store keeps the last 50 calls per session for detail, and cost and tokens are cumulative too. The rows are the table's. The Last write chip says only where the answering container's most recent session write landed, and reads memory on a container that has written nothing yet.
Session detail
Select a session to read it. The panel asks the service again, through GET /sessions/{id}, rather than showing the row a second time.
A freeze is the operator's kill switch, documented as POST /sessions/{id}/terminate. It writes a final state the service will not undo: every later call in the session is refused, and there is no unfreeze.
The service's own answer
Nothing requested yet.
Connection the API this page reads, and an optional key
A sign-in, and a key stored on the settings page, go only to the host that served this page. A key typed here goes wherever the address points.