Skip to content

Core concepts

Nori separates the agent doing the work from the infrastructure, credentials, and interfaces around it. The distinction matters because each part can change without replacing the others.

A session is one logical agent conversation and its work. In managed Nori, the session is assigned to a cloud machine, produces a transcript, can create checkpoints, and moves through a lifecycle from claim to release.

The logical session is more durable than one process or machine. An inactive conversation can often resume on another machine with its recorded context.

An agent is the coding product that reasons about the task, invokes tools, and returns a response. Managed Sessions currently supports Claude Code, Codex, Cursor Agent, OpenCode, and pi-acp as its first-class set.

The open-source CLI has a different support boundary: it includes Claude Code, Codex, and Gemini CLI configurations and can register custom ACP agents.

A harness hosts the agent loop and presents the user interface, session history, permissions, and tool plumbing. The Nori CLI is a harness. Managed Sessions can also launch supported agent harnesses inside a session machine.

The Agent Client Protocol (ACP) is a standard interface between a host and an agent process. ACP makes it possible to integrate an agent without rebuilding the surrounding terminal or session system.

The model provider supplies the model used by an agent. Its credential is not the same thing as the agent selection. Claude Code commonly uses Anthropic credentials, Codex uses OpenAI credentials, and other agents may expose their own credential schema or support multiple model providers.

Credentials can be organization-wide or per-user, depending on the integration. The broker stores and distributes them according to their type.

A skillset, called a personality in parts of Sessions, is a package of instructions, skills, and configuration applied to an agent. A fleet can have a default skillset, while a session or trigger can select another.

An integration connects the session to another system. Examples include GitHub, Google Workspace, Slack, managed MCP servers, and custom environment variables. The integration determines which credentials and capabilities reach the machine.

A fleet is an organization’s pool of session machines plus the defaults and policy that govern them. Fleet settings include capacity, lifecycle timeouts, agent and model defaults, skillset defaults, repositories, and access controls.

The broker is the service that coordinates a fleet. It receives work from Slack, Discord, the dashboard, the terminal, and triggers; claims machines; applies configuration; connects agents; records session state; and returns progress to the originating surface.

Hosted Nori organizations receive a single-tenant broker at an organization subdomain of norisessions.com.

The compute provider supplies the machine where a managed agent runs. It is independent of the coding agent and model provider.

  • Modal is the preferred hosted backend for new Nori fleets.
  • Sprites remains supported for existing hosted fleets.
  • AWS EC2 is available for dedicated bring-your-own-cloud deployments.
  • Docker provides a local deployment backend.
  • E2B exists as an internal alpha and is not a general customer option.

Compute is selected for a fleet or deployment, not for each prompt.

Slack, Discord, web, terminal, schedule, or webhook
|
v
broker
|
fleet policy + integrations
|
v
session on a compute backend
|
agent + model credentials + skillset

Continue with What is a session? or the support matrix.

this page as markdown: /start/concepts.md· index for agents: /llms.txt