Skip to content

Sessions quickstart

This quickstart takes a Nori organization from provisioning to its first managed coding-agent session.

You need:

  • A provisioned Nori organization and an owner or admin account.
  • Credentials for one supported agent.
  • A repository the agent is allowed to access.
  • A Slack workspace if you want to use the Slack flow.

If you are still choosing an agent, review supported agents and compute.

Sign in through login.norisessions.com. The login service resolves your organization memberships and sends you to the correct dashboard at <org>.norisessions.com.

Open Integrations and configure at least one first-class agent. Claude Code and Codex support Nori-managed API-key or OAuth paths. Other agents use the credential method declared by their registry entry.

Set the agent and model defaults in Fleet Setup. Defaults can later be overridden for a session or trigger when the selected agent is enabled.

In Integrations, install the GitHub App and select the repositories Nori may access. A personal access token is also supported, and it takes precedence when both methods are configured.

Then open Fleet Setup and add the repositories that should be prepared on session machines. The organization setup script can install dependencies or perform other repeatable workspace preparation.

Install the Nori Slack app from the Integrations checklist. In an allowed channel, mention the bot with a concrete, bounded task:

@nori reproduce the failing login test, fix the cause, run the focused suite,
and prepare a pull request

The bot replies in a thread. Continue by replying normally in that thread. You do not need to mention the bot again.

Useful commands:

  • !status shows the current session state.
  • !urls returns links for the session interfaces.
  • !interrupt <instruction> redirects the active turn.
  • !done ends the session and releases the machine.

Open Chat and submit the same kind of task. Web chat uses the same fleet and organization defaults as Slack. Session history remains available from the dashboard.

A healthy first run should show that a machine was claimed, the repository was prepared, and the selected agent started. Ask the agent to run a read-only check such as listing the repository or explaining its test command before giving it a larger task.

If the agent cannot authenticate, return to Integrations and verify the credential status. If the repository is missing, check the GitHub installation, repository selection, and Fleet Setup workspace list.

When the task is complete, use !done in Slack or the release control in the dashboard. Explicit release ends the session. Inactivity can wind down the agent process while preserving the logical session so a later reply can resume it.

See checkpoints and resume and the lifecycle reference for the exact contract.

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