Launch Grok Build CLI in a fresh side terminal without leaving your editor
Grok Build Launcher is a focused, local-first, unofficial VS Code extension for VS Code, Cursor, and Windsurf on Windows, macOS, and Linux. It opens the user-installed Grok Build CLI in a dedicated side terminal and stays out of the CLI's authentication and configuration.
Independent project. Grok Build Launcher is not affiliated with, endorsed by, sponsored by, or approved by xAI. Grok, Grok Build, xAI, and related names and trademarks belong to their respective owners. This repository contains original launcher assets and no official xAI or Grok artwork. See
TRADEMARKS.mdfor the complete notice.
| Channel | Action |
|---|---|
| Visual Studio Marketplace | Install the extension |
| Open VSX Registry | Install from Open VSX |
| GitHub Releases | Download the latest VSIX |
VS Code users can also install the Marketplace build from a terminal:
code --install-extension mikesoft.vscode-grok-build-launcherGrok Build CLI itself is a separate product. Install it from the official xAI documentation and confirm that grok works in an integrated terminal.
- Install Grok Build CLI and confirm that
grokworks in an integrated terminal. - Install Grok Build Launcher and open a trusted workspace or file.
- Select the launcher button in the editor title toolbar.
A fresh side terminal opens and starts grok in the relevant workspace folder.
- Editor-title toolbar launcher and Command Palette command
- A fresh side terminal for every launch
- Active-editor workspace selection with multi-root fallback
- Configurable executable command and terminal name
- Quoted Windows executable-path support
- Installation guidance through the verified official xAI documentation
- Bounded, memory-only missing-command diagnostics
- No automatic downloads, PATH edits, shell-profile changes, or telemetry
- VS Code
^1.103.0, Cursor, Windsurf, or a compatible editor - Grok Build CLI available in the integrated terminal environment
For development, use Node.js 22 and the committed npm lockfile.
| Setting | Purpose | Default | Scope |
|---|---|---|---|
grokBuildLauncher.cliCommand |
Command executed by the launcher. Workspace values are ignored. | grok |
Machine |
grokBuildLauncher.terminalName |
Base label for newly created terminals. | Grok Build |
Window |
Open the settings with Grok Build Launcher: Open Settings from the Command Palette.
Windows path containing spaces:
"grokBuildLauncher.cliCommand": "\"C:\\Program Files\\Grok Build\\grok.exe\""macOS or Linux absolute path:
"grokBuildLauncher.cliCommand": "\"/Users/you/.grok/bin/grok\""The extension does not require or read runtime environment variables. Local .env files are ignored by Git and must never contain publisher credentials or other secrets.
Grok Build Launcher does not collect telemetry, analytics, or personal data. Each launch creates a new terminal beside the current editor; when possible, the terminal starts in the workspace folder containing the active file, otherwise it uses the first open workspace folder.
For a direct grok launch, the extension may temporarily inspect at most the first 8 KiB of shell output to distinguish a missing executable from a normal CLI failure. The buffer exists only in memory, is discarded after the check, and is never persisted or transmitted. Custom commands and wrappers are not monitored.
Workspace Trust is enforced before command execution. grokBuildLauncher.cliCommand is read only from global or remote machine settings, and workspace-controlled values are ignored. The extension does not download or execute installers, run remote scripts, create temporary installation scripts, modify PATH, or edit shell profiles.
See SECURITY.md for the supported-version and disclosure policy.
Use the installation guide offered by the extension, or follow the official xAI installation documentation. Restart the editor if newly opened terminals still cannot find grok.
Confirm that the workspace is trusted. Then check grokBuildLauncher.cliCommand and verify the same command in a regular integrated terminal.
Quote executable paths that contain spaces, such as "C:\Program Files\Grok Build\grok.exe".
Open a file from the desired workspace folder before selecting the launcher. The active editor determines the preferred starting directory.
Requirements: Node.js 22 and npm with the committed package-lock.json.
git clone https://github.com/TheStreamCode/grok-build-launcher.git
cd grok-build-launcher
npm ci
npm run audit
npm run typecheck
npm run checknpm run check starts from a clean out/ directory, compiles the extension, runs unit and metadata tests, executes the VS Code Extension Host smoke test against the minimum supported version, and inspects the package file list. Set VSCODE_TEST_VERSION=stable to test the latest stable runtime.
To build the installable package:
npm run packageThe command creates vscode-grok-build-launcher-<version>.vsix and excludes tests, source maps, engineering documents, GitHub metadata, and local environment data. GitHub releases include the versioned VSIX and a SHA-256 checksum sidecar. Marketplace and Open VSX publication are separate maintainer-controlled steps. See CONTRIBUTING.md for contribution requirements.
- Report a reproducible bug
- Propose a focused enhancement
- Read
SUPPORT.mdfor diagnostic details and private contact options - Support ongoing maintenance through GitHub Sponsors
Need one interface for several coding agents? Super CLI provides a unified launcher for Claude Code, Codex, Copilot, Cursor, Grok, Kilo, Antigravity, OpenCode, and other supported tools.
See CONTRIBUTING.md. Pull requests must pass the required CI checks.
MIT License — see LICENSE.
Maintained by Michael Gasperini (Mikesoft). If this project is useful to you, consider sponsoring its maintenance.