Sessions & history
Every conversation with an agent is a session. Sessions persist, are searchable, and can be resumed — including a task that's still running when you close the tab.
Who can do what
| Task | User | Agent owner | Admin |
|---|---|---|---|
| See and search an agent's sessions | ✅ shared in | ✅ | ✅ |
| Resume a running task | ✅ shared in | ✅ | ✅ |
| Delete a session | ✅ shared in | ✅ | ✅ |
| Rate a message 👍 / 👎 | ✅ shared in | ✅ | ✅ |
| Open the debug view for a session | — | — | ✅ |
Sessions belong to the agent, not to the person who started them. Anyone the agent is shared with sees its history — worth remembering before you paste something private into a shared agent.
Recent tasks and the full list
The agent page shows Recent Tasks. Agent → Sessions is the full, paginated list, each session titled from its opening request (or its id, if the title hasn't been generated yet).
Searching
Search runs over titles and message content, combining semantic matching with fuzzy keyword matching — so "the invoice thing from last month" finds a session titled Q2 supplier reconciliation without an exact word in common.
Agents can search their own history too, with the search_sessions tool. That's
what lets an agent answer "what did we decide about the pricing model?" by
going and reading the earlier conversation rather than guessing.
Resuming a running task
Tasks keep running on the server when you navigate away or close the browser. Reopening the session reattaches to the live stream and you see the output from where it got to — no work is lost and nothing is duplicated.
If a task is going the wrong way, cancel it rather than waiting. Cancelling stops the work; anything already spent still counts toward budgets.
Feedback
👍 and 👎 on any agent message record whether the response was useful. Ratings are per person, so your rating and a colleague's are kept separately.
Deleting a session
Deleting hides a session from the agent's history. Its cost records are kept — they've already been billed, and removing them would misstate your usage. So deleting tidies your history; it isn't a way to undo spend.
Debugging a session
Admins can open Agent → Debug on a session to see the exact system prompt, the tool list the agent was given, its saved task state, and the raw message sequence. See Debugging a session.