gitwtfhub

wtf is grok-cc-plugin?

ivrylobs/grok-cc-plugin — explained in plain English

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 4/5Setup · moderate

TL;DR

A Claude Code plugin that delegates coding tasks to Grok while requiring approval before risky actions run.

Mindmap

mindmap
  root((grok-cc-plugin))
    What it does
      Delegates tasks to Grok workers
      Vetoes risky actions before they run
      Asks instead of guessing
    Tech stack
      TypeScript
      Claude Code plugin
      Grok CLI
    Use cases
      Delegate a bug fix to a Grok worker
      Review and approve risky tool calls
      Resume an interrupted worker
    Audience
      Developers
      Claude Code plugin users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Delegate a coding task to a Grok worker while Claude approves risky actions.

REASON 2

Let a worker pause and ask for missing information instead of guessing a secret.

REASON 3

Resume a worker session after it was interrupted, keeping its memory intact.

REASON 4

Adjust how much autonomy a worker has using different grip levels.

What's in the stack?

TypeScriptNode.jsClaude CodeGrok

How it stacks up

ivrylobs/grok-cc-plugin0xradioac7iv/tempfs52191314/web-agent-proxy-sdk
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatemoderatemoderate
Complexity4/53/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires Node 20+, a logged-in grok CLI account, and Claude Code restarted after plugin install.

No license information is stated in the README.

Wtf does this do

grok-cc-plugin is a Claude Code plugin that lets Claude hand off coding tasks to a separate AI model, Grok, while staying in control of what Grok is allowed to do. Instead of letting Grok run completely on its own, the plugin routes every file change and every risky command through a review step. Claude reviews and can approve or deny each risky action before it runs, so a worker never silently deletes files or runs a dangerous command without a person or Claude signing off first. The README describes two of its central behaviors with runnable proof rather than just claims. First, if Grok is asked to do something it does not have enough information for, such as filling in a real production secret key, it is designed to pause and ask a question instead of making up an answer. Second, every tool call a Grok worker wants to run, like creating a folder or running a shell command, is checked against a policy before it executes, and a denied action never actually happens. The project includes an offline test suite that can be run locally to verify these two behaviors, plus an optional live test that uses a real Grok account. Once installed, a person delegates a task to a Grok worker with a command like /grok:work, and a background process keeps track of the task so Claude gets notified when the worker finishes, asks a question, or needs a decision on a risky action. Other commands let a person check on running workers, approve or deny their pending requests, fetch a finished result, resume a worker that was interrupted, or stop one entirely. A separate setting called grip level controls how much a worker can do without asking first, ranging from a strict mode where every in-project file write is held for manual approval, to a looser mode where only a short list of destructive actions require sign-off. Installing it requires Node.js version 20 or later, the separate grok command line tool logged into a Grok account, and Claude Code itself. The plugin is installed as a Claude Code plugin marketplace entry and needs Claude Code restarted afterward so its commands load.

Yoink these prompts

Prompt 1
Help me install this plugin and log in to the grok CLI.
Prompt 2
Delegate a failing test fix to a Grok worker using /grok:work.
Prompt 3
Explain the difference between the gate, advise, and leash grip levels.
Prompt 4
Run the offline proof suite and explain what each test checks.

Frequently asked questions

wtf is grok-cc-plugin?

A Claude Code plugin that delegates coding tasks to Grok while requiring approval before risky actions run.

What language is grok-cc-plugin written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, Claude Code.

What license does grok-cc-plugin use?

No license information is stated in the README.

How hard is grok-cc-plugin to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is grok-cc-plugin for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.