Route mechanical implementation work like refactors and bug fixes to Grok while Claude keeps oversight.
Enforce a hard gate that blocks Claude's own edit tools during a session so work goes through Grok instead.
Dispatch several independent coding specs to Grok in parallel.
Run an external verification command to confirm Grok's changes actually pass before trusting its summary.
| rennlabs/grokdrive | 123satyajeet123/bitnet-server | ahloiscreamo/pod-search | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | Shell | Shell | Shell |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires the Grok Build CLI installed and authenticated on your system PATH alongside Claude Code.
grokdrive is an unofficial extension for Claude Code that splits coding work between two AI models. When turned on for a session, the Grok Build CLI does the actual implementation work while Claude stays in charge of planning, writing specs, reviewing, and verifying, without using its own file editing tools directly. The README describes this as a brain and body split: Claude is the brain making the judgment calls, and Grok is the body doing the typing. The way this is enforced is a hook that blocks Claude's own Write, Edit, MultiEdit, and NotebookEdit tools while the mode is active for that session. Instead, work is sent through a command called grokdrive, which passes a self-contained spec to Grok for execution. The README is direct that this hook only stops Claude's own edit tools, not file writes made through Bash commands, MCP tools, or spawned sub-agents, so it describes itself as strong friction and discipline rather than a full sandbox. Installing it requires Claude Code itself, the Grok Build command line tool on your system path, plus node, python3, and bash, since the installer and the gate script depend on all of them. After installing, the gate only takes effect in new Claude Code sessions started after that point. The tool includes commands to turn the mode on or off, check its status, dispatch a spec to Grok, dispatch several specs in parallel, and run a verification command against the actual code changes rather than trusting Grok's own summary. The README also lays out a routing guide for what kind of work should go to Grok versus stay with Claude: implementation from a frozen spec, mechanical refactors, bug fixes with a known reproduction, and test writing are suited to Grok, while design decisions, architecture, destructive operations, and review of Grok's own output are meant to stay with Claude. Configuration options include effort level, dispatch timeout, maximum turns per dispatch, and an environment variable that disables the gate entirely. The project is released under the MIT license.
grokdrive is a Claude Code extension that forces implementation work through Grok Build CLI while keeping planning and review with Claude.
Mainly Shell. The stack also includes Shell, Node.js, Python.
MIT license: use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.