Grok Build for VS Code
Use xAI’s Grok Build coding agent inside Visual Studio Code with native diffs, permission cards, file context, and ACP integration.
Use xAI’s Grok Build coding agent inside Visual Studio Code.
Grok Build is xAI’s agentic coding CLI. It can plan, edit files, run commands, use MCP servers, work with skills and plugins, and expose an ACP interface for other apps.
This page explains what Grok Build is, how it compares to Claude Code and OpenAI Codex, and how to use it inside VS Code.
What Is Grok Build?
Grok Build is xAI’s coding agent for software development.
It runs in the terminal, supports headless scripting, and can connect to other tools through the Agent Client Protocol, ACP.
You can use it to:
understand a codebase
edit files
run tests and commands
plan changes before writing code
use subagents
connect MCP servers
use skills, plugins, hooks, and memory
automate workflows from scripts or CI
Grok Build VS Code Extension
The Grok Build VS Code extension is a free, open-source sidebar client for Grok Build.
It is not a terminal launcher. It runs `grok agent stdio` in the background and talks to it over ACP.
The Grok CLI remains the engine. VS Code becomes the interface.
Features
VS Code sidebar chat for Grok Build
native diff preview before approving edits
permission cards for file and command actions
active file and selected text as context
session history
slash command autocomplete from the running Grok CLI
Agent, Plan, and YOLO mode controls
tool call rendering
collapsible thinking traces
MCP support through the Grok CLI
works beside Claude Code, Codex, Copilot Chat, and other tools
Install
First install and authenticate the Grok CLI from xAI:
macOS / Linux / WSL:
curl -fsSL https://x.ai/cli/install.sh | bashWindows (PowerShell):
irm https://x.ai/cli/install.ps1 | iexThen sign in:
grok /loginThen install the extension:
code --install-extension PawelHuryn.grok-vscode-phurynMarketplace: https://marketplace.visualstudio.com/items?itemName=PawelHuryn.grok-vscode-phuryn
Source code: https://github.com/phuryn/grok-build-vscode
Grok Build vs Claude Code vs Codex
Grok Build is the most experimental of the three. It runs through a terminal UI, headless mode, and ACP, with support for planning mode, subagents, MCP, and reusable workflows through skills, plugins, and hooks. Its main advantage is flexibility: it is a good fit for xAI users, ACP-based workflows, and people who want to experiment with Grok as a coding agent. VS Code support comes through this extension, and the ecosystem is still early.
Claude Code is the most mature Claude-native workflow. It spans terminal, IDE, desktop, and web surfaces, with an official VS Code extension, planning mode, subagents, MCP, and reusable workflows through instructions, skills, and hooks. It is best for builders who already use Claude heavily and want the most established coding-agent environment.
OpenAI Codex is the strongest fit for OpenAI-native coding workflows. It works across CLI, IDE, cloud, and ChatGPT, with official IDE support, planning mode, subagents, MCP, and reusable workflows through AGENTS.md and workflow instructions. Like Claude Code, Codex is a mature ecosystem, but it is optimized around OpenAI’s broader product surface.
Grok Build vs Claude Code
Claude Code is currently the more mature coding-agent ecosystem.
Use Claude Code if you want the most established Claude-native workflow, official editor support, and mature docs around instructions, MCP, subagents, hooks, and permissions.
Use Grok Build if you want to experiment with xAI’s coding agent, use Grok’s CLI, or build around ACP.
Use the VS Code extension if you want Grok Build inside your editor instead of only in the terminal.
Grok Build vs Codex
Codex is OpenAI’s coding agent. It has strong support across CLI, IDE, cloud tasks, and ChatGPT.
Use Codex if you already work in the OpenAI ecosystem.
Use Grok Build if you want xAI’s agent stack, Grok-specific models, ACP integration, and compatibility with Grok’s skills, plugins, hooks, and MCP setup.
Is Grok Build Better Than Claude Code or Codex?
Not universally.
The better question is which workflow fits your setup:
choose Claude Code for mature Claude workflows
choose Codex for OpenAI-native coding workflows
choose Grok Build if you want to test xAI’s agentic coding stack
use the VS Code extension if editor-native review, diffs, and permissions matter to you
Most serious builders will probably use more than one coding agent.
FAQ
What is Grok Build?
Grok Build is xAI’s agentic coding tool. It can run in a terminal UI, headlessly in scripts, or through ACP for integration with other applications.
Does Grok Build work in VS Code?
Yes. This extension brings Grok Build into VS Code as a sidebar UI.
Is this an official xAI extension?
No. It is an independent open-source extension and is not affiliated with xAI.
Do I need the Grok CLI?
Yes. The extension requires the Grok CLI. It is a UI layer over `grok agent stdio`.
Is the extension free?
Yes. The extension is free and open source.
Is Grok Build open source?
The VS Code extension is open source. Grok Build itself is xAI’s product.
Can I use Grok Build with MCP servers?
Yes. Grok Build supports MCP servers through the CLI. The extension uses whatever MCP setup the CLI loads.
Can I use Grok Build with AGENTS.md?
Yes. Grok reads AGENTS.md-style instruction files according to xAI’s docs.
Can Grok Build read Claude Code files?
xAI documents Claude Code compatibility, including Claude instruction files, skills, plugins, MCPs, agents, and hooks.
What is ACP?
ACP stands for Agent Client Protocol. It lets external apps communicate with Grok Build as an agent process. This extension uses ACP to connect VS Code to `grok agent stdio`.
Links
Install from VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=PawelHuryn.grok-vscode-phuryn
GitHub source: https://github.com/phuryn/grok-build-vscode
xAI Grok Build docs: https://docs.x.ai/build/overview