Nori vs Grok Bot

Quick answer

It depends on the job. Grok Bot is a persistent general-purpose bot: one user's Bots share a long-lived computer and keep skills, memory and routines, and teams can add Bots to Slack. Nori is a team engineering workspace: it ships Jiro, its own AI engineering teammate, runs any coding harness on your own Claude or ChatGPT subscription, never charges for tokens, and gives every task its own isolated sandbox. Pick Grok Bot for standing personal work; pick Nori for team software work that ends in a reviewed pull request.

What is Grok Bot?

Grok Bot is an always-on agent product documented in Cursor's docs. You create Bots and give them standing jobs. This page compares Grok Bot with Nori, as of November 2026, using those docs.

Several facts changed since we first wrote this comparison in October, so here is what the current pages say.

• One persistent computer per user, shared by that user's Bots. The current Grok Bot docs describe a persistent computer shared by one user's Bots. It is not one computer per Bot, as earlier coverage (including ours) said.
• Skills, memory and routines. Bots keep what they learn and can repeat saved work on a routine.
• Team Bots in Slack. The Grok Bot for teams docs describe Slack Team Bots.
• Enterprise can turn it on. The team docs describe Enterprise enablement. The older statement that enterprise access was by waitlist only is obsolete.
• Model choice is unknown. We previously wrote that Grok Bot ran only one vendor's models with no picker. The pages we read in November do not re-establish that, so we no longer claim it either way.
• Price is unknown. The Grok Bot pages we read do not state a price or a usage rate. Check Cursor's pricing page for the plan that applies to you.

Grok Bot is a different product from Cursor's cloud coding agents, which have their own plans, self-hosted workers and automations. Those are covered in Nori vs Cursor cloud agents.

What is Nori?

Nori is a cloud platform for coding agents, built for engineering teams. People start and steer sessions from Slack, Discord, the web or the CLI. Cron schedules, one-time reminders and webhooks start the same kind of session, with run history and approval paths. Projects give long-running work a coordinator, shared docs and subworkers.

Each session runs in its own isolated cloud sandbox with your repositories, your team's skillset and scoped credentials. Nori runs any agent harness: Claude Code, Codex, Gemini CLI, Cursor, OpenCode, Droid, Amp, or any ACP agent. You connect your own Claude or ChatGPT subscription, API keys or LLM gateway, and Nori never charges for tokens.

Meet Jiro

Jiro is Nori's own AI engineering teammate, built for software work that ends in a pull request. Jiro runs on the subscription or API key you connect, so there are no token charges. It follows an opinionated engineering workflow: plan, write the test first, implement, review. On its first day it reads your repositories, asks the team how you ship, and sets up the workspace. See jiro.bot.

Nori vs Grok Bot, head to head

The machine row matters more than it looks. A persistent computer shared by one user's Bots suits standing personal work, because state carries over. A fresh sandbox per session suits team code changes, because two tasks cannot step on each other's checkout and each session only holds the credentials it was given.

Enterprise deployment: where does the control plane run?

The control plane is the service that decides who may start a session, runs the agent loop and keeps the record. See what an agent control plane is.

The Grok Bot pages we read describe a persistent computer for each user's Bots and Enterprise enablement by an admin. They do not describe running the computer or the control plane on infrastructure you own. Treat that as unknown and ask the vendor if your security team needs it.

Nori Enterprise deploys the full stack, control plane included, into your own AWS VPC or Azure VNet, or on-prem. It uses your identity provider (SAML, SCIM, OIDC), your LLM gateway and your compute. On hosted plans, Nori gives each organization a dedicated, single-tenant control plane and data store, and every session runs in its own isolated sandbox.

A worked example: the same standing job on Nori

Suppose a Bot currently runs a morning routine: check which dependencies have new releases and tell the team. On Nori, the same job becomes an automation that produces pull requests, not only a message.

Schedule: 30 7 * * 1   (Mondays, 07:30)
Prompt:   In web-app and api-gateway, list dependencies with a new minor or patch release.
          Open one PR per repository. Run the test suite before you push.
          Post the PR links and any failing tests in #platform.
Approval: PRs need one human review before merge.

Each Monday run gets a fresh sandbox per repository, the team's skillset, and the credentials the automation owner is allowed to use. The run appears in the automation's history. When a reviewer replies in the Slack thread, the same session picks the comment up:

@nori the api-gateway PR bumps grpc past what our proxy supports. Pin it to 1.64 and rerun.

Nothing about the job depends on one person's computer or one person's Bot. If the owner is on holiday, anyone in the channel can steer it.

When to choose Grok Bot

• The work is personal and standing. A Bot that keeps its own computer, skills and memory suits chores one person owns.
• The work is not mainly code. Grok Bot is a general-purpose bot. Nori is built for software engineering and the review steps around it.
• You want state to persist on one machine. A user's Bots share a persistent computer, so state carries from one run to the next.
• You want routines without writing cron. Routines are a documented Grok Bot feature.
• Your team already works in the Cursor ecosystem. Grok Bot is documented alongside Cursor's other products, and Enterprise admins can enable it.

When to choose Nori

• The work is software engineering for a team. Requests from Slack, schedules and webhooks all end in a pull request that a person reviews.
• You want a ready-to-work AI engineer. Jiro plans, works test-first and reviews its own changes, in the thread where the request was made.
• You want to choose the harness and the model. Run Claude Code, Codex, Gemini CLI or any ACP agent, and switch when a better one ships.
• You already pay for Claude or ChatGPT. Nori uses those subscriptions, or your API keys or gateway, and never charges for tokens. See do cloud coding agents mark up token costs.
• You need isolation between tasks. Every session gets its own sandbox and scoped credentials.
• You want shared context. Org skillsets and shared memories belong to the team, so every session starts with how your team ships.
• Security needs the control plane inside your boundary. Nori Enterprise runs in your cloud with your identity provider and LLM gateway.

Many teams will use both: a Bot for one person's standing chores, Nori for the team's pull requests.

How to switch from Grok Bot to Nori

1. List the coding work your Bots do. For each routine, write down its timing, its instructions, and where it posts results. Leave non-code chores where they are.
2. Start the 30-day free trial. No card is needed.
3. Connect models. Sign in with your Claude or ChatGPT subscription, or add API keys or your LLM gateway.
4. Recreate each routine as an automation. Timed routines become cron schedules. Anything that should react to an event becomes a webhook. See scheduled coding agents.
5. Move Bot skills and memory into team context. Reusable instructions become skills in your org skillset. Standing facts about your codebase become shared memories.
6. Install Nori in Slack or Discord so the team can start and steer sessions from chat. See the Slack coding agent.
7. Run both for a week on the same routines, compare the results, then retire the Bot routines you have replaced.

For the wider field, see cloud coding agents compared or Nori vs Claude Tag. To see it on your own repositories, book a demo.

Frequently asked questions

Sources

Competitor facts were read from these vendor pages on November 11, 2026. Vendors change plans and features often; check the source before you decide.

• Cursor docs: Grok Bot
• Cursor docs: Grok Bot for teams (Slack Team Bots, Enterprise enablement)
• Cursor: Pricing
• Cursor docs: Self-hosted cloud agents (a separate product)
• Cursor docs: Cloud agent automations (a separate product)
• Claude: Pricing (subscriptions Nori can reuse)
• OpenAI: ChatGPT pricing (subscriptions Nori can reuse)