Home / Cursor / Grok Build 2.0 Review
AI Coding IDE & CLI · November 2026Cursor Renamed to Grok Build 2.0: What Changed, Model Access & How to Migrate
Following SpaceX's acquisition of Cursor, pre-release builds delivered via the Cursor CLI (2026.11.19) signal a unified Grok Build 2.0 channel combining Cursor's editor and CLI backend with xAI's terminal coding agent (grok).
Updated November 22, 2026 · Preview rollout details can evolve rapidly; confirm current plan terms and CLI commands on x.ai and cursor.com.
Direct answer: what developers need to know right now
What is changing: Standalone Cursor branding is transitioning toward Grok Build for desktop, web, and unified CLI/TUI workflows (while preserving familiar elements like Cursor's cube icon and Composer models). Unified preview builds accept both Grok and legacy Cursor accounts and surface roughly 38 models across xAI Grok, Claude, Gemini, and Composer.
What to wait on: Final enterprise seat pricing, third-party model quota rules, and GA dates remain in preview rollout. Keep your repository instructions in a portable root AGENTS.md and compare Cursor alternatives before locking annual contracts.
Legacy Cursor vs. Grok Build 2.0 preview: side-by-side breakdown
| Dimension | Legacy Cursor | Grok Build 2.0 (Unified Preview) |
|---|---|---|
| Primary surface | Desktop IDE (VS Code fork) + separate cursor-agent CLI |
Unified desktop/web app + consolidated terminal TUI agent (grok / CLI 2026.11.19) |
| Authentication | Cursor account | Grok account or legacy Cursor account; headless CI via XAI_API_KEY |
| Model selection | Cursor Composer + Claude, OpenAI, Gemini tiers | Expanded ~38-model pool including native xAI Grok (e.g., Grok 4.7), Claude, Gemini, and Composer |
| Rules & extensibility | .cursor/rules, MCP JSON config |
Native MCP CLI (grok mcp add), hooks, plugins, AGENTS.md, and /skillify |
| Billing routes | Cursor Pro / Business / Enterprise seats | X / xAI subscription pools (Plus, Premium, Super, Ultra) or pay-per-token xAI API; third-party model billing varies by route |
How to prepare your workflow & connect MCP tools
- Keep rules portable: Move shared engineering standards out of editor-only files into root
AGENTS.mdso Grok Build 2.0, legacy Cursor, Claude Code, and Codex CLI all read the same guardrails. - Separate interactive and CI keys: Sign in with your workspace Grok or Cursor account for desktop/TUI work, and reserve
XAI_API_KEYwith explicit spend limits for automated CI/CD jobs. - Attach scoped MCP servers: Register remote HTTP or local stdio MCP servers with read-only permissions first, then verify approval prompts before granting write or shell access.
# Connect a remote HTTP MCP server in Grok Build CLI
grok mcp add --transport http docs-search https://mcp.example.com/mcp
# Package a verified troubleshooting session into a reusable skill
/skillify
For a full technical migration walkthrough covering .cursor/rules, SKILL.md structure, and MCP permission checks, see the Grok Build 2.0 Skills & MCP Migration Guide on AgentSkillsHub.
Who should adopt early vs. hold on legacy Cursor
Try Grok Build 2.0 preview if
- You already pay for an X / xAI subscription or xAI API and want native Grok 4.7 alongside Claude/Gemini in one TUI and IDE.
- You rely heavily on terminal-first agent loops,
/skillifysession capture, and CLI-managed MCP servers.
Hold or evaluate alternatives if
- Your organization requires locked annual enterprise procurement terms, SOC 2/DPA sign-off, or predictable third-party model rate cards before migrating off legacy Cursor.
- You want non-xAI editor ecosystems—compare Cursor alternatives such as Claude Code, Codex CLI, Windsurf, or GitHub Copilot.
Frequently asked questions
Is Cursor officially becoming Grok Build 2.0?
Developer pre-releases via the Cursor CLI (2026.11.19) point to a unified Grok Build 2.0 channel combining Cursor's editor/CLI stack with xAI's terminal agent following SpaceX's acquisition of Cursor. Confirm GA rollout timelines on official xAI and Cursor channels.
Will existing Cursor accounts and Claude/Gemini models still work?
Preview builds accept both Grok and legacy Cursor accounts and expose roughly 38 models including Grok, Claude, Gemini, and Composer. Exact quotas and third-party model surcharges depend on your plan.
How is Grok Build 2.0 priced?
Access spans X / xAI subscription pools for interactive use and pay-per-token API billing via XAI_API_KEY for headless runs. Confirm final pricing tiers and third-party model billing on x.ai and cursor.com.