Grok Build,
in your notch.

Q: Why doesn’t Gnista show anything for Grok?

Start a new grok session after connecting.

Grok Build notifications on your Mac

Gnista shows every Grok Build session in your MacBook’s notch: working, done, or waiting for you. You see the command it’s running and its reply when the turn ends, and one click takes you to its tab to answer.

Try free for 7 days No account, no card · then €19 once

01At a glance

Gnista with Grok Build, at a glance.

Where it runs: Grok Build (grok) in any terminal.
Setup: Its own hooks file, ~/.grok/hooks/gnista.json.
Needs you: Permission prompts and questions, the moment Grok asks.
Answer from the notch: No: Grok’s hooks can’t approve, so Gnista takes you to the tab.
Reply from the notch: Typed into its terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
In the row: The command it runs or the file it reads or edits, and its reply when the turn ends.
Subagents: Not yet.
Cost and limits: Tokens, context and cost, from Grok’s own session record, with the cost xAI counts; no plan limits.

Know when it’s waiting for you.

When Grok asks permission or asks you a question, the notch says so at once, and a click lands you in the exact tab, ready to answer. Interrupt a turn, and the row shows it as done.

Every step, in one line.

The row follows Grok from your prompt through the commands it runs and the files it reads, searches and edits, and shows its reply when the turn ends.

One agent, one row.

Grok Build also runs the hooks in Claude Code’s settings. Gnista knows when Grok is the one running them and leaves those out, so a Grok session never shows up as Claude.

What it can’t do with Grok Build, and why.

Answering from the notch: Grok’s hooks can’t approve a tool, and Grok still asks in its own prompt, so you answer in Grok.
What it’s asking: Grok’s permission notice doesn’t name the tool, so the notch says Grok needs you, and the row shows the command it was on.
Subagents don’t show on the row yet.
Plan limits: Gnista doesn’t show any for Grok, only what each session cost.
Replies from the notch are typed into its terminal, so only in Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.

02Setup

Connected in a minute.

Open Gnista and tick Grok Build.
Gnista writes its hooks to a file of its own, ~/.grok/hooks/gnista.json. Your other hook files stay as they are.
Start a new grok session. Grok reads every file in ~/.grok/hooks/, with no trust step.

03FAQ