Operating
Sessions and runs
A session is the sandbox your agent works in, with its own data, trace, and expiry. Nobody shares one with you.
The lifecycle
| Phase | What applies |
|---|---|
| Created | No account. You get the address and the config snippet right away. |
| Active | Every tool call extends the session. |
| Finished | 15 minutes after the last tool call — or 2 hours after creation at the latest. Before the first call only the 2-hour limit applies. |
| Viewable | The trace stays readable for 24 hours after that. |
| Deleted | Session and trace are deleted together. |
An agent that's thinking looks exactly like one that's gone. That is why idle time ends a session, not a call count.
Reset instead of starting over
A reset puts the session's data back to its starting state. The trace survives — so you can still see what the previous run did.
That's the difference from a new session: a new one would have different records and different IDs. Comparing two prompt variants needs exactly the same starting point, or the second run measures the mess the first one left.
Limits on an open demo
The demo runs without a login, so there are caps. They're set where a real test run won't notice them:
- A cap on tool calls per session — in the hundreds, not the dozens.
- A cap on how much data one session may hold. It's good for thousands of records.
- A rate limit per IP address, both for new sessions and for tool calls.
Hit a cap and the response says so and names the way out. No cap makes a call quietly do something else.
Deleting
A session that hasn't seen a single tool call can be deleted right away. Once calls are recorded, the trace is the thing you're looking at — so the session expires on its normal schedule instead.