Grok Build, xAI's AI-powered coding agent, now has native Windows support through a PowerShell installer released May 25, 2026, alongside existing macOS and Linux options. The command-line tool with an interactive terminal interface (TUI) had previously required Windows developers to use WSL2 (Windows Subsystem for Linux), a workaround that sometimes caused inconsistent behavior. The new PowerShell path offers a more direct installation route for Windows users who prefer not to set up a Linux environment.

What Changed for Windows Developers?

For most of Grok Build's early beta period, the documented Windows installation path was WSL2, which required developers to work within a Linux environment running on Windows. While functional, this approach added friction for developers unfamiliar with Linux tools or those who simply wanted a native Windows experience. The May 25 PowerShell installer changed that equation. Windows developers now have two legitimate paths: stick with the established WSL2 route or try the newer PowerShell installer.

The timing matters because Grok Build remains in early beta, with access limited to specific xAI subscription tiers. According to launch documentation, access is available to SuperGrok Heavy subscribers and X Premium+ subscribers. This subscription-based access gate is enforced during authentication, not during installation, which means the install command succeeds regardless of your subscription level. The real access check happens when you first launch the tool and sign in with your xAI account.

How to Install and Set Up Grok Build on Your System

• macOS Installation: Run the curl command to download and execute the install script, which works natively on both Apple Silicon and Intel Macs without additional setup.
• Linux Installation: Use the same curl-based install script as macOS; the tool is natively supported on Linux systems.
• Windows via PowerShell: Run the PowerShell installer command in a PowerShell session (not Command Prompt) to install Grok Build directly on Windows without WSL2.
• Windows via WSL2: If you already use WSL2, run the Linux install script inside your WSL environment; this path remains functional and stable.
• Authentication Setup: On first launch, Grok Build opens a browser window for OAuth authentication; sign in with the account holding your eligible xAI subscription to gain access.
• Headless Environments: For CI pipelines or servers without browser access, set the GROK_CODE_XAI_API_KEY environment variable with an API key from console.x.ai instead of using browser-based authentication.

What Should You Verify Before Installing?

The most common setup problem is a successful installation followed by authentication failure. This happens because Grok Build's access control is subscription-based, not API-key-based. You can install the tool without an eligible subscription, but you won't be able to use it. Before spending time troubleshooting your terminal, confirm that your xAI account holds a SuperGrok Heavy or X Premium+ subscription. The official xAI documentation should be your source of truth for current eligibility requirements, as beta access tiers may change.

Once installed and authenticated, Grok Build operates on the repository in your current working directory. Change into your project folder before launching the tool, then run the inspect command to confirm that Grok detected your project configuration, including any AGENTS.md files, skills, MCP servers, hooks, and plugins. This verification step prevents surprises when you trust the agent with actual code changes.

How Does Grok Build Actually Work?

Grok Build is a command-line tool with an interactive terminal UI, not a standalone desktop application. You run it in your terminal and interact with it through structured back-and-forth sessions. The tool's signature feature is Plan Mode, which generates a graph of sub-tasks with per-node state displayed in your terminal. Instead of a linear text plan, you describe a high-level objective like "add rate limiting to the Express middleware with Redis," and Grok Build creates a structured plan showing which files to modify and which commands to run. You review and approve before execution.

For automation, Grok Build supports headless mode via the -p flag, allowing it to run in CI pipelines, cron jobs, and scripts without the interactive TUI. The tool also supports the ACP (Agent Client Protocol) for deeper automation integration. By default, Grok Build runs on grok-build-0.1, a coding-specific model with a 256K-token context window that accepts text and image input. The tool also supports model flexibility, allowing you to route requests through OpenRouter to use Claude, GPT, or local language models through the same CLI.

Does Grok Build Work With Your Existing Configuration?

A key design decision in Grok Build is zero-migration compatibility with Claude Code's configuration format. If you're migrating from Anthropic's Claude Code, your existing CLAUDE.md file works without changes. Grok Build automatically discovers and loads standard agent configuration including AGENTS.md files, skills in the Anthropic skill format, MCP servers that are already configured, and hooks and plugins from standard locations. This compatibility means you can switch tools without rewriting your project's agent configuration.

The Windows PowerShell installer represents a maturation step for Grok Build's cross-platform support, though xAI's documentation notes that a fully mature native Win32 build remains on the roadmap without a committed date. For now, the PowerShell installer offers Windows developers a practical middle ground between the friction of WSL2 and the eventual arrival of a fully native Windows application. As an early beta addition, the PowerShell path may have rough edges that the more established macOS and Linux paths don't, so monitoring the official xAI documentation for updates remains important.