grokpack is a companion suite of Grok Build for Claude Code, positioned as a three-in-one solution for "observe, drive, display." It is itself a lightweight umbrella project responsible for installing, updating, and documenting tools dedicated to Grok Build; each component has its own independent repository, and this suite serves only as a unified entry point. It does not bundle multi-engine fuse/route tools (such as fleet-fuse, peer, etc.); multi-engine orchestration belongs to a separate cross-model layer.
In terms of purpose, grokpack provides three components: grokprint for observation (orientation card), grokdrive for driving (executed by Grok, orchestrated and gated by Claude), and grok-hud for displaying a HUD in tmux. The suite does not implement these functions itself; instead, it serves as a unified installation and management entry point, bringing together tools from their respective independent repositories.
Main capabilities: After installation, the suite CLI will appear in PATH at ~/.local/bin/grokpack. Component resolution order is: first read the environment variable GROKPACK__DIR, then look for sibling directories under the parent of this directory (for example ~/repos/grokprint), and finally git clone from Rennlabs/. After installation or update, grokpack.lock pins component versions@sha. grokdrive's gating only takes effect in Claude Code sessions started after installation, so you need to start a new session before running grokdrive on. grokprint's hooks can be reloaded in Grok via Ctrl+L → Hooks → r. If ~/.local/bin/grok-hud is a regular file (an old copy), you can use ./install.sh --force to handle it.
Usage: .claude-plugin/marketplace.json lists the plugin-form components (grokprint, grokdrive), but that file is a draft; before relying on it, validate it against the current Claude Code marketplace schema. Standalone plugin-form installation can still be done via each component's own ./install.sh, or by placing the repository into a marketplace you control. Eachpublic release should run the Update playbook in the registry. For complete guidance on when to use each tool, see docs/routing.md.
Applicable scenarios: Users who need to observe, drive, and display in coordination with Grok Build in Claude Code can use grokpack to uniformly manage components such as grokprint, grokdrive, and grok-hud. Multi-engine orchestration (fleet-fuse / FrontierFuse / peer) belongs to an independent cross-model layer and is outside the scope of this suite.
Limitations: This project is an unofficial suite, not affiliated with xAI, and is a best-effort companion solution; logos and component APIs may change at any time without notice. Release-related: MIT © 2026 Renn Labs.
