Skip to content

Nori FAQ

Nori is infrastructure for running coding agents as shared team services. The managed Sessions product supplies isolated cloud machines, a broker, integrations, session history, checkpoints, and organization policy. The open-source CLI and Skillsets projects provide a local ACP terminal and portable agent configuration.

Nori can start coding-agent work from Slack, Discord, a web dashboard, a terminal, schedules, reminders, and webhooks. It can prepare repositories, connect approved tools and credentials, apply a team skillset, stream progress, preserve the transcript, and resume eligible sessions after inactivity or a machine change.

See What can Nori do? for examples and boundaries.

Which coding agents does Nori Sessions support?

Section titled “Which coding agents does Nori Sessions support?”

The default first-class Sessions set is Claude Code, Codex, Cursor Agent, OpenCode, and pi-acp. Additional ACP registry agents can be gated behind a feature flag, but they are not part of the default support promise.

Gemini was removed from managed Sessions. It remains available in the separate open-source Nori CLI.

No. Nori runs and coordinates coding agents. You connect the credential required by the selected agent, such as an Anthropic or OpenAI API key, an OAuth login, a Cursor API key, or an OpenAI-compatible endpoint for OpenCode and pi-acp.

Model availability still depends on the connected provider account and plan.

Nori CLI and Nori Skillsets are open source. Nori Sessions and Handroll are the managed product. The CLI source is at tilework-tech/nori-cli, and the Skillsets source is at tilework-tech/nori-skillsets.

Each session runs on a machine from the organization’s configured fleet. Modal is preferred for new hosted fleets, while Sprites remains supported for existing hosted fleets. Dedicated deployments can use AWS EC2 for BYOC or local Docker workers. E2B is an internal alpha, not a general customer option.

One claimed machine serves one active session within the organization’s fleet. The exact isolation mechanism depends on the compute backend, such as Modal gVisor sandboxes, Sprites VMs, private AWS EC2 instances, or local Docker containers. See security and credential boundaries for details.

The organization broker stores integration configuration and distributes the required material to session machines. Handling varies by type: OAuth refresh credentials can remain broker-side while refreshed access tokens are pushed; API keys and custom values are written into protected environment or agent configuration files; per-user Google access follows the scopes that user granted.

The docs do not claim that every credential is short-lived, because custom secrets and provider keys may be long-lived.

Yes, when the session has repository access and the selected agent is asked to make and verify a change. Nori supports GitHub App installation access or a personal access token. The agent’s actual ability to push a branch or open a pull request depends on the granted GitHub permissions and its approval policy.

Can Nori run tasks without a person online?

Section titled “Can Nori run tasks without a person online?”

Yes. Cron triggers run recurring jobs, reminders run once at a future time, and webhooks react to external events. Trigger changes are admin-gated, and run history records success or failure.

Often, yes. Transcripts and checkpoints let eligible sessions resume after the agent process stops or the underlying machine changes. In Slack, a normal reply can revive an inactive session unless someone explicitly released the thread with !done or !release.

Interactive surfaces can change the agent and model within organization policy. An agent switch can move the logical conversation to a fresh machine. Transcript context carries over, but uncommitted working files do not automatically move with it.

The organization can choose open, guarded, or strict access for people driving the bot. A separate setting controls the agent’s own Slack reach, with channel-only as the default and broader modes available for deliberate use.

Current offers and trial terms are published on the Nori pricing section. Documentation avoids copying a price that may change independently from the product site.

Every documentation page has a raw Markdown twin by appending .md to its path. The site also publishes /llms.txt as a concise map and /llms-full.txt as the complete corpus. HTML pages publish canonical metadata and structured TechArticle data.

Use the Nori quickstart to choose managed Sessions or the open-source CLI. For Sessions, continue to the Sessions quickstart.

this page as markdown: /resources/faq.md· index for agents: /llms.txt