What is Nori?
Nori is infrastructure for running AI coding agents as dependable members of a team. It moves agent work off one developer’s laptop and into isolated cloud sessions that can be started from Slack, Discord, a web dashboard, a terminal, a schedule, or a webhook.
Nori does not replace Claude Code, Codex, or another coding agent. It provides the runtime around them: machines, lifecycle, credentials, integrations, transcripts, checkpoints, team policy, and portable skillsets.
The problem Nori solves
Section titled “The problem Nori solves”A coding agent can edit a repository locally, but team use creates a broader systems problem:
- Where does the agent run when no developer laptop is available?
- How does a teammate start or continue the work from Slack?
- Which repositories, credentials, and external tools may the agent access?
- What survives when the process stops or the machine is recycled?
- How does the same team guidance reach different agent products?
Nori makes those concerns part of one platform rather than a collection of one-off scripts.
The four parts of Nori
Section titled “The four parts of Nori”Sessions
Section titled “Sessions”Nori Sessions is the managed product. A single-tenant broker maintains a fleet of session machines for an organization, claims a machine when work starts, connects the selected agent and integrations, and streams progress back to the surface that started the work.
Sessions can be interactive or unattended. Slack, Discord, the web dashboard, and Handroll support conversations. Triggers support scheduled jobs, one-time reminders, and inbound webhooks.
Handroll
Section titled “Handroll”Handroll is Nori’s terminal interface for interactive agent sessions. It supports attach, detach, resume, and handoff workflows so an agent conversation is not tied to one terminal window.
The open-source Nori CLI is a local terminal host for agents that speak the Agent Client Protocol (ACP). It includes built-in configurations for Claude Code, Codex, and Gemini CLI, plus custom ACP agent registration. The CLI owns the terminal experience, session history, approval policy, MCP forwarding, hooks, and sandbox controls while the selected agent remains a separate process.
Skillsets
Section titled “Skillsets”The open-source Nori Skillsets project packages reusable agent instructions and tools. It translates a skillset into the file layout used by supported agents, which lets a team maintain one source instead of copying instructions by hand.
Managed and open-source paths
Section titled “Managed and open-source paths”You can use Nori at two levels:
| Path | Best for | You operate |
|---|---|---|
| Managed Sessions | Teams delegating work through shared surfaces | Repositories, integrations, policy, agent choice |
| Open-source CLI and Skillsets | Developers composing a local agent workflow | The machine, credentials, agent process, and configuration |
The paths can be used together. A team might define behavior in Skillsets, test it locally through the CLI, and use the same skillset in managed Sessions.
Who Nori is for
Section titled “Who Nori is for”- Engineering teams that want agents reachable from Slack or a browser.
- Platform teams that need controlled credentials, repeatable environments, and fleet-level policy.
- Developers who want one terminal for multiple ACP agents.
- Teams that need scheduled maintenance, webhook reactions, or other background agent runs.
- Organizations that want agent instructions to be portable across products.
What Nori is not
Section titled “What Nori is not”Nori is not a foundation model, a proprietary coding engine, or a replacement for source control. It runs and coordinates supported agents, supplies the environment and integrations they need, and records the work they perform.
Next steps
Section titled “Next steps”this page as markdown: /start/what-is-nori.md· index for agents: /llms.txt