Nori Sessions
Nori Sessions is the managed runtime for team-operated coding agents. An organization gets a single-tenant broker and a fleet of isolated session machines. When work starts, the broker claims a machine, prepares the workspace, applies the selected skillset, distributes configured credentials, launches the agent, and streams progress back to the originating surface.
Why teams use Sessions
Section titled “Why teams use Sessions”Sessions solves the infrastructure around an agent rather than replacing the agent itself:
- Start work from Slack, Discord, the web dashboard, Handroll, schedules, or webhooks.
- Keep repositories and setup logic consistent across session machines.
- Connect GitHub, Google Workspace, MCP servers, and custom environment values.
- Select an agent, model, and skillset through organization defaults or session controls.
- Preserve transcripts and checkpoints so work can resume after inactivity or a machine change.
- Control who may start sessions and how far an agent can reach into Slack.
Supported agents
Section titled “Supported agents”The first-class Sessions set is Claude Code, Codex, Cursor Agent, OpenCode, and pi-acp. This is not the same list as the open-source Nori CLI. Gemini CLI remains available in the local CLI but is not a supported Sessions agent.
See supported agents and compute for the current matrix and credential notes.
What happens when a session starts
Section titled “What happens when a session starts”- A user or trigger submits a task to the broker.
- The broker validates access and resolves agent, model, skillset, and workspace defaults.
- A ready machine is claimed from the organization’s fleet.
- Repositories, setup instructions, and configured credentials are applied.
- The selected agent starts and receives the task.
- Progress and results return to Slack, Discord, the dashboard, or the trigger run record.
- The session becomes idle, resumes later, or is explicitly released.
The detailed states and timeouts are documented in the session lifecycle reference.
Interactive and unattended sessions
Section titled “Interactive and unattended sessions”Interactive sessions expect a person to continue the conversation. Slack, Discord, web chat, and Handroll all fit this model.
Unattended sessions come from triggers. A cron schedule, reminder, or webhook can start work when nobody is online. Triggered runs use the same fleet, agent resolution, integrations, and lifecycle as other sessions, with run history and failure state recorded by the broker.
Organization boundary
Section titled “Organization boundary”Hosted organizations use a dedicated broker at <org>.norisessions.com. The
broker owns organization membership, fleet settings, session state, and
credential distribution. Machines belong to that organization’s fleet and are
recycled by its lifecycle policy.
Documentation map
Section titled “Documentation map”- Quickstart: connect an agent, repository, and Slack workspace, then run a first task.
- Guides: use Slack, the dashboard, integrations, and triggers.
- Concepts: understand sessions, fleets, credentials, checkpoints, agents, and skillsets.
- Handroll: work with sessions from a terminal.
- Reference: verify support, lifecycle, configuration, and limits.
this page as markdown: /sessions.md· index for agents: /llms.txt