Skip to content

Grok Build security on your Mac

Excellent for Mac is free to scan. It reads Grok Build's logs and shows what it did. With Pro, it checks each action before it runs.

Works with Grok Build

Trademarks belong to their owners; no endorsement implied.

What Excellent sees

Excellent reads Grok Build's session logs in ~/.grok/sessions on your Mac: each call, when it ran and how it ended.

It shows what was done: your email sent to websites or typed into forms, keys sitting in logs, secrets files read, history overwritten, checks skipped. Each finding says which agent and where.

With Pro, while the app runs, it reads Grok Build's logs as they grow, and sends you a notification when something new needs you.

Its key finder checks Grok Build's config for keys, and reports its sign-in files without changing them.

What it can stop Pro

This needs Excellent Pro. Free and Pro says what each does.

Turn on protection, and Excellent writes its own hook file, ~/.grok/hooks/excellent.json, which Grok Build runs before each action. Grok Build also runs Claude Code's hooks, so the check reaches it through those too, once per action.

It blocks your email on its way to a website, an API key typed into a command, deleting a folder you marked never-delete, and switching Excellent off.

It asks you first before a force push to main, skipping git hooks, typing your email into a web form, or writing over a file you marked never-delete.

Two more rules are off until you turn them on: asking before reading keys and .env files, and asking before breaking a rule you wrote in CLAUDE.md or AGENTS.md.

You can stop a Grok Build session from Excellent's menu: its actions are refused until you press Continue. One Grok process runs sessions one after another, so Excellent can't end a session on its own. Stop it in Grok.

Excellent can also pause a session by itself when it breaks one of four rules: sending your email to a website, deleting or moving a never-delete folder, reading a never-open file, or overwriting history on main. Setup asks about this, with all four ticked.

Tested in Grok Build 1.0.62 on a Mac: the check Turn On adds ran there, refused what it should, and let a harmless command through.

Your rules

Sharing works between Claude Code and Codex. Grok Build doesn't get your rules from it.

Grok Build reads CLAUDE.md and AGENTS.md itself, so rules you wrote there reach it. Rules only in Grok's own rule files, in ~/.grok/rules, aren't read by Excellent.

With Pro and Remind agents of my rules on, the check refuses an action that would break a rule you wrote in CLAUDE.md or AGENTS.md once, and quotes your rule. Reminders are off by default.

The sandbox Pro

Excellent's sandbox covers Claude Code and Codex. Grok Build gets the live check only.

What isn't covered

  • Excellent's sandbox doesn't cover Grok Build, so nothing backs the check up there.
  • The check reads what a command says. An agent set on getting around it sometimes can.
  • A script file run by an interpreter, like python3 cleanup.py, isn't read by the check.
  • If the check can't answer within 10 seconds, Grok Build goes ahead, as its hooks are built to. Excellent answers in under 3 seconds, or asks.
  • A Grok Build session's helpers show up as sessions of their own.
  • If you switch Excellent's hook off in Grok's Hooks tab, Excellent shows Grok Build as not protected, and leaves turning it back on to you.

Set it up

  • Get the Mac app. It needs an Apple silicon Mac and macOS 14 or later. Protection needs Pro.
  • With Pro, open it and press Protect My Agents. It lists what it will change first, then adds its check to ~/.grok/hooks/excellent.json. Turn On in the menu does the same later.

Install the Mac appTurn on protectionStop or pause an agentThe agents it supports

The other agents

Protect Grok Build on your Mac

Get the Mac app