What is a Nori session?
A Nori session is one logical agent conversation and its work. Managed Sessions binds that conversation to a machine from the organization’s fleet, starts the selected coding agent, records the transcript, and tracks the run until it is resumed, restarted, or released.
The session is the durable concept. The machine and agent process can change while the conversation remains resumable.
What belongs to a session
Section titled “What belongs to a session”A session resolves and records:
- The organization and user or trigger that started it.
- The originating surface, such as a Slack thread or web chat.
- The selected agent, model, and skillset.
- The assigned fleet machine.
- A transcript of messages and agent events.
- Checkpoint metadata used for restoration when supported.
- Lifecycle timestamps and terminal state.
Lifecycle
Section titled “Lifecycle”The broker keeps a pool of machines so sessions do not begin with a full machine provisioning cycle. At a high level, each machine moves through:
bootstrapping -> ready -> claimed (active <-> idle) -> dead- Bootstrapping: Nori creates and prepares a machine.
- Ready: the machine waits in the fleet pool.
- Claimed: a request assigns the machine to one session.
- Active: the agent is processing a turn.
- Idle: the conversation is waiting between turns.
- Dead: the machine has been released or cannot continue.
Exact states and timeouts are generated from the product source in the lifecycle reference.
How a session starts
Section titled “How a session starts”A Slack mention, Discord message, web chat, Handroll request, schedule, reminder, or webhook reaches the broker. The broker validates access, chooses a ready machine, applies the organization’s workspace and skillset, distributes the configured credentials, launches the selected agent, and submits the prompt.
Active, idle, and released are different
Section titled “Active, idle, and released are different”An active session has a turn in progress. An idle session is still claimed but is waiting for input. An inactive process may be stopped to save resources while the conversation remains resumable.
Explicit release is different. In Slack, !done or !release ends the session
and makes the thread human-only. A normal reply no longer restarts the agent
until a new mention creates another session.
What survives a machine change
Section titled “What survives a machine change”The transcript and checkpoint records are the continuity layer. When a session resumes on a new machine, Nori can restore supported state and provide the agent with the conversation context it needs to continue.
Working-directory persistence depends on the checkpoint mechanism and compute backend. Do not treat a session machine as permanent storage. Commit durable repository work and store other important outputs in an appropriate connected system.
Session isolation
Section titled “Session isolation”One session receives one machine from its organization’s fleet. The machine runs as an isolated environment supplied by the active compute backend. The exact kernel, snapshot, suspend, and lifecycle capabilities vary by backend.
See security and credentials for trust boundaries and fleets and compute for backend differences.
this page as markdown: /sessions/concepts/what-is-a-session.md· index for agents: /llms.txt