Session Agreed
The industry's term · its card
Definition
A session keeps one run of an agent together, its context, its record and its place, so the work can be followed and resumed.
A session is one run of an agent: a conversation with its own context, its own id and the folder it works in. It is made of turns, each a request and the agent's work on it. The agent harness runs the session and keeps its transcript, the record of every turn, so the session can be resumed later with its context intact.
A session is also made of threads. The agent's own line of work is its primary thread, and each subagent it starts works in a thread of its own within the session. A thread is a part of a session, never another word for one.
Specifications
- Agent Client Protocol (ACP): its session, a close match.
- Agent Host Protocol (AHP): its session and the chats inside it. Only a chat spawned by a tool call is a thread in this card's sense, a subagent's; a chat the user makes, a fork or a side chat is a conversation of its own, nearer an ACP session.
Our conventions
The Knowledge Islands system already says session in this sense, as in the ki-acquire skill's agent-session acquisition and the housekeeping skills' session inventories, and has no convention of its own to map onto it.
Next
A subagent is an agent started by another agent to do part of its work, in a thread of its own.
What each vendor calls it
- Anthropic
- Session (exact), Conversation (close)
- Session (exact), Conversation (close)
- Microsoft
- Agent session (exact), Chat (related)
See the crosswalk for every term side by side.