Reinventing.AI
ReferenceUpdated 2026-10-17• 13 harnesses

AI Agent HarnessesWhere your agent actually lives

A harness is the program around the model: the chat, the file access, the tools, the scheduler and the approval gate. Most of them now read the same skill format, so the choice is smaller than it looks. This page compares them on what differs and ends with a sixty second way to pick one.

What a harness does that the model does not

The model reasons. The harness decides how instructions are read, how tools run, when a person is asked for approval, how sessions persist, how work resumes in the background, and how the agent reaches you: in a terminal, a chat app, a browser or an API. That layer is where practical value is won or lost.

In 2026 the category split into distinct shapes. Some harnesses are code first and terminal native. Some are operator layers that live in chat apps and run cron jobs overnight. One runs on its own cloud computer. The comparison below is organised around those differences rather than around feature lists.

The reason the choice is low stakes: every harness on this page reads the Claude Code skill format, a folder with one file that says how a job gets done. Standards, skills and routines move with you. The harness is a residence, not a marriage.

The parts every harness has

  • ✓A conversation surface: terminal, desktop app, editor, chat app or web UI
  • ✓File and shell access on a real machine
  • ✓Tool calling, including MCP servers and browser control
  • ✓A scheduler for recurring work, or a hook into the operating system's
  • ✓An approval gate for anything that sends, spends or deletes
  • ✓Session memory so work resumes where it stopped

The comparison

Four things actually separate these tools: where the agent runs, how recurring work is scheduled, which models it can drive, and whether you can read the source.

HarnessRunsSchedulingModelsSourceBest for
Claude Code logoClaude Code
Anthropic
Your machine, in a terminal or the Code tab of Claude DesktopScheduled tasks, built inClaude models, with Claude Opus 5.5 as the default Opus since September 22, 2026 and Claude Sonnet 5.5 added on September 28, 2026Proprietary client, open skill formatThe default starting point, and the harness the Agent Ops Club builds and tests everything on
Codex logoCodex
OpenAI
Your machine, terminal CLI, plus cloud tasksScheduled runsOpenAI models, with GPT-6.1 Sol the default in Codex since Codex CLI 0.159.1 on September 29, 2026, GPT-6.1 Sol Ultrafast available in Codex and ChatGPT Work since October 8, 2026, and GPT-6 Sol and GPT-6 Luna still selectable at lower token prices than the GPT-5.6 generationOpen source CLITeams whose stack and subscriptions already live on OpenAI
OpenCode logoOpenCode
Open source community
Your machine, terminalRecurring runsAny provider; model agnostic by designOpen sourceOperators who want to switch models freely without rebuilding their setup
Grok Bot logoGrok Bot
xAI
Its own cloud computer: a virtual machine with a browser, a terminal and file accessRoutines it saves and runs on a schedule, on its own machineGrok modelsProprietary, in beta for SuperGrok and Cursor subscribersAlways on operation without building a VPS yourself
OpenClaw logoOpenClaw
Open source community
Your machine or a VPS, reached through WhatsApp, Telegram, Discord, Slack and other chat appsCron jobs and heartbeats, built inAny major providerOpen sourceChat first, always on operator work across messaging surfaces, with an open source enterprise control plane on top when the team needs it
Hermes logoHermes
Nous Research
Self hosted on your machine or server, with Telegram, Discord and Microsoft Teams surfacesRecurring jobsMany providers, plus an OpenAI compatible local proxy for other clientsOpen sourceAmbitious self hosters who want one harness to absorb the whole frontier
Pi logoPi
Mario Zechner
Your machine, terminal, headless with a single flagNone of its own; use the operating system's schedulerAny providerOpen sourcePeople who want to see every moving part
Cline logoCline
Cline
VS Code extension, plus a CLI that runs without the editor openIts own cron in the CLIAny providerOpen sourceAnyone who already lives in VS Code all day
Qwen Code logoQwen Code
Alibaba
Your machine, terminal, headless with qwen -pScheduled tasks, built inQwen models first, with OpenAI, Anthropic and Gemini keys acceptedOpen sourceOperators whose first question is cost per run
DeepSeek logoDeepSeek
DeepSeek
A local server with a web interface, launched as dshA plugin, like everything else in itDeepSeek models, with models as pluginsOpen sourceEarly adopters who want a plugin shaped harness to watch
Antigravity logoAntigravity
Google
Your machine, as an agent first editor plus the agy command lineThe agy job runnerGemini models first, with other frontier models selectableProprietaryTeams on Google's stack who want an editor built around agents and a job runner for the scheduled work
Muse logoMuse
Meta
Two shapes: Muse Code in your terminal on macOS and Linux, and Muse, the personal agent, on a dedicated cloud VM of Meta'sMuse Code: in session loop jobs that stop when the terminal closes, so the operating system's scheduler. Muse: crons on its own cloud machineMuse SparkProprietary. Muse Code is in beta on paid usage tiers; Muse has a free tier and two paid onesOperators on Meta's stack, and anyone weighing a cloud personal agent against Grok Bot
Dots logoDots
OpenAI
Its own cloud computer with its own browser, reached from ChatGPT on desktop, web and mobile, and from Slack and TeamsAlways on: it works toward your goals in the background around the clock and messages you with progress, questions and decisionsGPT-6 AstraProprietary. Rolling out in ChatGPT to Pro and Business Premium in eligible markets, with an Enterprise beta; the first dot is included in the planOperators already on ChatGPT who want an always on agent that reaches them in Slack or Teams

Also reads the format, no icon on this page yet: .

Each harness, honestly

Claude Code logo

Claude Code

by Anthropic

Claude Code runs in a terminal or inside Claude Desktop, reads and writes real files, runs real commands, and schedules recurring work. It defined the skill format that the other harnesses on this page read, which is why it is the reference implementation for most operator kits published today. As of v2.1.302 (October 15, 2026) it ships Claude Mods, the TypeScript based extension system Anthropic announced on October 1, 2026: small functions that hook into Claude Code's events to rewrite prompts before they reach the model, block or retry tool calls, approve or deny permission requests, redact secrets from tool output, and redraw parts of the interface. Mods ship inside plugins, run in the CLI and the desktop app, and are the path the team has been using to ship features like /diff and AGENTS.md support, with more built ins moving to mods over time. v2.1.300 (October 14, 2026) extended the mod system with a prompt.change hook that fires whenever the prompt box's text changes through recall, clear, undo, or a plugin fill, and let a mod rewrite a workflow agent's prompt and model in agent.spawn rather than only refusing; the same release added /advisor on Claude Platform on AWS so an opt in advisor model can steer the agent away from avoidable work, plus OpenTelemetry GenAI semantic convention attributes for trace spans. v2.1.296 (October 7, 2026) earlier added onFailure: "block" for command and HTTP hooks, OSC 7501 working state in supporting terminals, and several session resume fixes. v2.1.283 (September 25, 2026) had added AGENTS.md fallback when no CLAUDE.md is present and shipped plugins through a new developer portal.

Best for
The default starting point, and the harness the Agent Ops Club builds and tests everything on
Running a scheduled routine
Native format. Leave a kit where you extracted it and register each routine as a scheduled task pointed at its folder. Routines are scheduled work, not on demand skills, so they do not belong in a global skills directory. A mod is a separate layer that wraps Claude Code itself: use it when a routine needs to rewrite how a prompt is sent, intercept a tool call, or draw new UI around an existing workflow, and keep mods in their own plugin rather than mixing them into a routine folder. As of v2.1.300, a mod's prompt.submit hook can also read the bytes of images or documents attached to the prompt, which makes it a clean place to enforce a routine's input policy before work begins.
Codex logo

Codex

by OpenAI

OpenAI's agent harness is capable, especially on code heavy work, and the natural pick when the whole team already runs on OpenAI. The Claude Code skill format works there with minor adjustment. Codex CLI 0.159.0 shipped on October 1, 2026 as a major refresh: a new full screen interface, keyboard navigation across older task history, a /voice command for spoken turns, Mermaid and LaTeX rendered directly in the terminal, collapsible diffs and tool output, and a one day follow up in 0.159.1 that made GPT-6.1 Sol the new default model. OpenAI added GPT-6.1 Sol Ultrafast to Codex and ChatGPT Work on October 8, 2026 for Pro $500 and eligible Enterprise and Edu plans, with Enterprise access off by default and workspace owners controlling availability. Earlier in the wave, Codex CLI 0.156.1 (September 23, 2026) had added the first fullscreen TUI, worktree sessions by default, and bundled native voice runtimes.

Best for
Teams whose stack and subscriptions already live on OpenAI
Running a scheduled routine
Drive the cadence with Codex scheduled runs, one job per routine, each handed that routine's SKILL.md as the run prompt.
OpenCode logo

OpenCode

by Open source community

OpenCode is open source and model agnostic, which is its actual pitch: point it at different models and keep the working setup you already have. Worth it when model flexibility matters more than polish.

Best for
Operators who want to switch models freely without rebuilding their setup
Running a scheduled routine
Reads the Claude Code skill format directly. Mirror the schedule table into its recurring runs, one run per routine folder.
Grok Bot logo

Grok Bot

by xAISince August 2026

Grok Bot arrived in August 2026 as something structurally different: every other harness here runs on your machine, while a Grok Bot gets its own cloud computer. It signs into the tools you use, keeps working while your laptop is shut, and comes back when something needs approval. The October 2026 releases reshaped both its team shape and its price of entry. xAI added Team Bots on September 28, 2026 so a Grok Bot can be given shared files, apps, and expertise and then handed to the rest of the team to work from the same context. The X Subscription on October 12, 2026 folded Grok Bot into a single plan alongside Grok chat, Cursor, and X Premium, with Grok Bot included on the $30 Premium tier for new customers and drawing from a weekly shared pool across Grok, Grok Bot, and Cursor. v0.68.0 added right-click routine controls and clearer approval cards, while v0.68.1 raised the cloud screen to 1920 x 1200, sped up computer actions and screenshots, and added slide deck and formatted email draft workflows. Grok Voice 3.0 shipped on October 14, 2026 as grok-voice-3.0 on the xAI API at the same price as Grok Voice 2.0, so Grok Bot's voice turns now run on the same frontier speech model xAI sells.

Best for
Always on operation without building a VPS yourself
Running a scheduled routine
The closest native fit for scheduled routines. Create one recurring task per routine and hand it that routine's SKILL.md as the run prompt; as of v0.68.0, routine rows can be paused, resumed, tested, edited or deleted from the details pane. Under The X Subscription (October 12, 2026) Grok Bot usage draws from a weekly shared pool with Grok and Cursor, so a heavy routine week can also be a heavy coding week, and Super and Ultra give the larger pool for that case.
OpenClaw logo

OpenClaw

by Open source community

OpenClaw is built around always on operation, with recurring work as cron jobs and the agent reachable from the chat apps you already use. The overnight and VPS patterns that operator kits teach map onto it directly. It is the harness this site covers most deeply. On September 29, 2026 the OpenClaw Foundation announced OpenClaw Enterprise (OCE), a vendor neutral, MIT licensed control plane for deploying persistent OpenClaw agents on an organization's own infrastructure, developed in the open with OpenAI, Red Hat and NVIDIA and already piloted inside both Red Hat and OpenAI. OCE adds multi-tenancy, hard security boundaries between trusted and untrusted workloads, LLM based reviews, fine-grained permissions and a standardized agent lifecycle, while leaving the harness, model, and sandbox swappable for third party or internal implementations.

Best for
Chat first, always on operator work across messaging surfaces, with an open source enterprise control plane on top when the team needs it
Running a scheduled routine
Reads the same SKILL.md format. Register each routine's schedule as an OpenClaw cron job pointed at the kit's routines folder.
Hermes logo

Hermes

by Nous Research

Hermes is the widest open harness in the field: many providers, many chat surfaces, browser and local runtimes, and a local proxy that lets other agent clients borrow its providers. Breadth is the point, and also the cost, so it is a better second harness than a first one.

Best for
Ambitious self hosters who want one harness to absorb the whole frontier
Running a scheduled routine
Point Hermes's recurring jobs at the kit's routines folder and mirror the cadence in SCHEDULE.md, one job per routine.
Pi logo

Pi

by Mario Zechner

Pi is a deliberately minimal terminal agent: extensions, skills and prompt templates, and not much else on purpose. It reads skills folders directly and runs headless with one flag, so recurring work goes through cron or Task Scheduler rather than a built in scheduler.

Best for
People who want to see every moving part
Running a scheduled routine
Reads skills folders directly and runs headless with pi -p. Mirror the schedule table into the operating system's scheduler, one job per routine, with the kit folder as the working directory.
Cline logo

Cline

by Cline

Cline started as the VS Code extension many people met agents through, and now ships a CLI with its own cron for agents that run without a terminal open. Open source, any model provider, and the shortest walk for an editor first workflow.

Best for
Anyone who already lives in VS Code all day
Running a scheduled routine
Register one scheduled task per routine with cline schedule create, handed that routine's SKILL.md as the prompt, with auto approve on so a run never hangs.
Qwen Code logo

Qwen Code

by Alibaba

Alibaba's open source terminal agent is tuned for the Qwen models but takes other providers' keys too. It reads skills, has scheduled tasks and runs headless. The Qwen models are among the cheapest that can do this work, which makes it the budget pick.

Best for
Operators whose first question is cost per run
Running a scheduled routine
Reads the skill format and ships scheduled tasks. Register one per routine, or drive qwen -p from the operating system's scheduler, one run per routine folder.
DeepSeek logo

DeepSeek

by DeepSeekSince August 2026

DeepSeek's harness runs as dsh and arrived in August 2026 as an open source system where everything is a plugin: models, tools, skills, scheduling, even the interface. It runs a local server with a web interface rather than a chat in the terminal. Newest on this list and moving fastest.

Best for
Early adopters who want a plugin shaped harness to watch
Running a scheduled routine
dsh runs a local server and scheduling is one of its plugins. Register one scheduled run per routine, handed that routine's SKILL.md as the prompt, with the kit folder as the working directory.
Antigravity logo

Antigravity

by Google

Antigravity is Google's agent first development environment: agents plan, run and verify work across the editor, a terminal and a browser, and report back with artifacts a person can review. Its agy command line runs the same agents headless, which is what makes scheduled routines possible on it. Antigravity 2.17.0 (September 22, 2026) led with 'Plan before you build', and the same week added native Windows support, programmatic turn cancellation, and a nine level MCP safety policy precedence model in the SDK 0.1.18 release on September 21, 2026.

Best for
Teams on Google's stack who want an editor built around agents and a job runner for the scheduled work
Running a scheduled routine
Schedule each routine with the agy job runner, pointed at the routine folder rather than registered as a global pack.
Muse logo

Muse

by MetaSince August 2026 (Muse Code), September 2026 (Muse)

Meta shipped two things in a month: Muse Code, a terminal coding agent, on August 5, 2026, and Muse, a personal agent that lives on a dedicated cloud VM with connectors, skills and crons, on September 8, 2026. Muse Code reads the Claude Code skill format directly and imports existing skills with one command, connects MCP servers, and runs headless with muse exec. Muse itself is the Grok Bot shape: a machine of its own that keeps working after you close the app and comes back when it needs approval.

Best for
Operators on Meta's stack, and anyone weighing a cloud personal agent against Grok Bot
Running a scheduled routine
On Muse Code, mirror the schedule table into the operating system's scheduler, one job per routine, each running muse exec with approvals disabled and the routine's SKILL.md as the prompt; its built in loop jobs do not survive a closed terminal. On Muse, the first check is whether its cloud machine can reach your signed in accounts at all.
Dots logo

Dots

by OpenAISince September 2026

OpenAI announced dots on September 29, 2026 as always on agents rather than a chat window or a coding terminal. Each dot has its own cloud computer, its own browser and the apps you connect through plugins, over 4,000 of them by OpenAI's count, and you can open its computer at any time to inspect its work. It learns your preferences from feedback, can be called on a voice call, and can be given permission to use your laptop alongside you. Custom Rules let you allow, require approval for or block specific actions, and Activity View shows background work as it happens.

Best for
Operators already on ChatGPT who want an always on agent that reaches them in Slack or Teams
Running a scheduled routine
Dots is the hosted shape Grok Bot set: the kit lives on the dot's own cloud computer, so give it each routine's SKILL.md as the task and check first that it keeps the files between runs and can reach the accounts the routine reads. Its background research uses read only tools, and certain sensitive actions, such as changing a password, always stay with you.

The skill format is the portable layer

A skill is a folder with a file in it, SKILL.md, that says how one job gets done. Once installed, the agent reads it whenever that job comes up. By the third time you explain the same process to an agent, you should stop explaining and start installing.

Every harness on this page reads that folder. The differences that matter are mostly naming: Claude Code calls recurring work scheduled tasks, OpenClaw calls them cron jobs, Cline has its own cron in the CLI, and Pi hands the schedule to the operating system. They function the same way.

One rule holds everywhere: a scheduled routine is pointed at its own folder, never copied into a global skills directory. Routines are scheduled work, not on demand skills.

Use a second harness for second opinions

An agent does not have to be the only one working. It can drive another harness's command line, hand off a job, keep working while that job runs, and read the result when it comes back. Three reasons to set this up:

  1. A genuinely independent set of eyes. A second opinion from the same model in the same session shares its context and blind spots. A different model reading the same code fails in different places, which is the entire value of a review.
  2. Parallelism. A full repository audit runs in the background while the main agent stays responsive.
  3. Cost spread across subscriptions you already pay for. Long audits and research sweeps go to a provider you are already subscribed to, so the primary tokens go on orchestration and verification.

Choosing in sixty seconds

The decision guide from Reinventing.AI's Agent Ops Masterclass, where the harness lesson opens by deflating the question: everything the club ships runs on all of these.

  1. 01
    Already paying for Claude?
    Use Claude Code. Stop reading, go to the next section.
  2. 02
    Already deep in OpenAI, or the team is?
    Use Codex.
  3. 03
    Starting from nothing and want the machine to keep running without you?
    Look at Grok Bot first.
  4. 04
    Need to switch models freely?
    OpenCode.
  5. 05
    Already in VS Code all day?
    Cline.
  6. 06
    Still undecided after sixty seconds?
    Claude Code. The harness you start today beats the harness you research for a week. Every hour spent comparing is an hour your first routine is not running.

The ten minute test

Before committing to any of them, take any skill folder, hand it to the harness, and ask it to summarise what the skill does and when it would use it. A harness that reads the folder correctly will run everything else. A harness that cannot is telling you in ten minutes what you would otherwise learn over a week.

The cloud harness tradeoff

A cloud harness signs into your accounts from a machine you do not control. That is a real tradeoff rather than a dealbreaker. Handle it the way you would handle a contractor with credentials: a separate browser profile, no password manager attached, and access to nothing you would not hand a new hire on their first morning.

Related reading on this site

Compare harnesses with a repeatable test

A transparent test protocol and downloadable evaluation worksheet.

Find your starting shortlist

A free selector based on your workflow and ecosystem preferences.

The Agent Operations field guide

Learn permissions, recovery, evaluation, costs, and memory.

Claude Code Guide: Hooks, Plugins, and Running Claude Code as an Agent Harness

The pillar page for operating Claude Code: deterministic control with hooks and the function hooks preview.

Claude Code Hooks: The Complete Guide

From a first hook in the desktop app to seven copy and paste examples and the function hooks proposal.

OpenClaw vs Hermes vs Claude Code: The State of AI Agent Harnesses in May 2026

A release notes only snapshot of the three harnesses with the most momentum.

AI Agents Are Starting to Ship as Operator Harnesses for Small Team Workflows

Why the category is separating models with tools from real operating layers.

AI Agents Are Moving Toward Open Eval Harnesses Small Teams Can Run

How small teams test agents before trusting them with real work.

Claude Code vs OpenClaw

The long form comparison of the two harnesses this site covers most.

Installing OpenClaw

The setup walkthrough for the chat first, always on harness.

OpenClaw Trends: v2026.9.6 Adds Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7

The September 24, 2026 OpenClaw release wired every flagship model into one Gateway, alongside the week long Anthropic, OpenAI, and xAI launch wave.

OpenClaw Decision Models: TypeSafe Jev and Local Choices Land in v2026.9.6

Optional Decision Models on the same September 24, 2026 release, with TypeSafe Jev and locally chosen decision back ends.

Operator Eval Coverage: Why Repeatable Harness Tests Are Now a Board Level Concern

A September 21, 2026 look at the open eval harnesses solo operators and small teams are actually running on Claude Code, Codex, OpenClaw, Hermes, and Cline.

Frequently asked questions

What is an AI agent harness?

A harness is the program an AI agent lives in: the chat, the file access, the tools, the scheduler and the approval gate around the model. The model reasons; the harness decides how instructions are read, how tools run, how work persists between sessions and how the agent reaches a person. That layer is where practical value is won or lost.

Which AI agent harness should a beginner choose?

The Agent Ops Masterclass recommends Claude Code for almost everyone, through the Code tab in Claude Desktop, because every published operator kit was built and tested there and there is nothing to configure. Pick Codex if the team already lives on OpenAI, Grok Bot if the machine needs to keep running without you, OpenCode to switch models freely, and Cline if you spend the day in VS Code.

Do skills and routines transfer between harnesses?

Yes. Every harness on this page reads the Claude Code skill format: a folder with a SKILL.md file describing one job. Standards, skills and routines move with you, so the harness is a residence rather than a marriage. The differences are mostly naming: Claude Code calls recurring work scheduled tasks and OpenClaw calls the same thing cron jobs.

Which harnesses run in the cloud instead of on my machine?

Grok Bot, Muse and Dots are the ones on this page that get a cloud computer of their own, a machine with a browser and file access that keeps working while your laptop is shut. Grok Bot and Dots arrived within weeks of each other, and Dots is the version that lives inside ChatGPT, Slack and Teams. OpenClaw and Hermes are commonly run on a VPS for the same always on effect, but you set that up yourself.

Which harness is cheapest to run?

Qwen Code, because the Qwen models it is tuned for are among the cheapest that can do agent work, and it accepts other providers' keys when a task needs a stronger model. Open source harnesses like OpenClaw, OpenCode, Hermes, Pi and Cline cost nothing themselves; you pay only for the model API.

Can one harness use another as a second opinion?

Yes, and it is worth setting up. An agent can drive another harness's command line, hand off a job, keep working while it runs, and read the result. A different model reading the same code fails in different places, which is the whole value of a review, and it spreads cost across subscriptions you already pay for.

Did the major harnesses ship a coordinated release in late September 2026?

Yes. Between September 21 and 25, 2026, Anthropic, OpenAI, xAI, OpenClaw, and Google shipped model and harness updates inside a 48 hour window. Anthropic launched Claude Opus 5.5 on September 22, 2026 as the first model in the Claude 5.5 family, with a one million token context window and a price 40 percent below Opus 5; Claude Code v2.1.283 followed on September 25 with AGENTS.md fallback support and a new plugin developer portal. OpenAI rolled GPT-6 Sol and GPT-6 Luna into Codex between September 21 and 25 at lower token prices than the GPT-5.6 generation, and shipped Codex CLI 0.156.1 on September 23 with a fullscreen TUI, worktree sessions by default, and bundled native voice runtimes. xAI shipped Grok 4.7 on September 17, 2026 with a 500k context window, with Grok Build 1.0.40 following on September 20. OpenClaw v2026.9.6 on September 24 wired Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7 into the Gateway chat model lineup, alongside a complete 30 day Usage report, managed update recovery, and a new GitHub reader. Google Antigravity shipped 2.17.0 'Plan before you build' on September 22, with the Antigravity SDK 0.1.18 adding native Windows support, programmatic turn cancellation, and a nine level MCP safety policy precedence model on September 21. The combined effect for an operator with one laptop is that the choice between a Claude, OpenAI, or xAI powered routine is now a model picker decision inside one harness rather than a reason to switch harnesses.

What changed when xAI launched The X Subscription in October 2026?

On October 12, 2026, xAI (now trading as SpaceXSI) replaced SuperGrok, X Premium, and the standalone Cursor plans for new customers with a single plan family called The X Subscription, in five tiers: Free, Plus at $8 a month, Premium at $30, Super at $100, and Ultra at $200. For the first time Grok chat, Grok Bot, Cursor, and X Premium sit on one bill with one usage pool. Grok Bot is included on Premium, Super, and Ultra and draws from a weekly shared pool across Grok, Grok Bot, and Cursor; the Plus tier does not include Grok Bot. Cursor's pricing page now sells The X Subscription instead of its old Pro and Ultra plans, and only Grok models are available on Plus. Existing SuperGrok, Cursor, and X Premium subscribers are being offered the option to switch with a prorated refund for unused time, but no one is forced off their current plan. For an operator, the practical effect is that the cheapest route into Grok Bot for a new account rose from $20 a month on Cursor Pro to $30 a month on The X Subscription Premium, but the same bill now also covers Grok chat, voice, image and video generation, Cursor's coding agents, and X Premium; third party models in Cursor remain available on Premium and above at API list price. Team and Enterprise tiers add SSO, admin controls, consolidated billing, usage analytics, and SOC 2 compliance, and a single usage pool across both products.