Zest
Docs / Grok Build

Zest for Grok Build

Add the marketplace, install with --trust, and log in.

Grok Build logo

The first /zest-login takes ~40 seconds while the plugin downloads its runtime (~24 MB). Grok buffers slash-command output, so nothing appears until it finishes. This is expected, not a hang.

Install

New to Zest? Step 4 opens your browser, where you can create your account. Free for 3 seats, no credit card.

Create a free account
  1. 1

    Add the Marketplace

    In a terminal, add the official Zest marketplace for Grok Build:

    grok plugin marketplace add Winding-Labs/zest-grok
  2. 2

    Install the Plugin

    Install Zest and trust it so session hooks can run. --trust is required; without it capture stays off.

    grok plugin install zest@zest-grok --trust
  3. 3

    Reload Plugins

    If Grok was already open, type this and press r so /zest-login appears. Skip if you started a new session after install.

    /plugins
  4. 4

    Authenticate with Zest

    Inside a Grok session run the Zest login command. Do not use Grok's built-in /login — that is xAI auth. Grok may also show Claude Code's /zest:login (with a colon); that one signs in Claude Code, not Grok, so use /zest-login (with a dash).

    /zest-login
  5. 5

    Start coding

    The plugin tracks Grok Build sessions in the background. /zest-status shows auth, sync, and hook health.

Check it works

Zest has no status line in Grok Build, so the status command is the one place to look. Inside a Grok session it shows your account and workspace, what synced and what is queued, the current Grok session, the daemon, hook health, and whether this folder is tracked.

/zest-status

What it captures

What it reads on your laptop

  • Grok's session files in ~/.grok/sessions/: each session's summary and updates.

What it uploads

  • Your prompts and Grok's replies, as text.
  • Each session's title (Grok's own), folder name, model, per-turn token counts and context use.
  • How many times each tool was used, as counts.

When it syncs

/zest-login adds a hook Grok runs when a session starts (~/.grok/hooks/zest.json). It starts a background daemon that reads and uploads every 60 seconds. A session uploads once it has 3 messages. A folder seen for the first time is read from midnight that day, and your first sign-in imports up to 10 of today's sessions.

What stays on your laptop

  • Secrets. Every text field is checked against 89 patterns (API keys, tokens, passwords, private keys, email addresses and more) and a match is replaced with [REDACTED] before it leaves your laptop. The API runs the same patterns again. The patterns.
  • Text your workspace does not collect. If you or an admin turned off prompts or agent replies in Settings → Privacy, that text is left out of the upload.
  • Grok's reasoning, tool calls and their output, images, diffs and file contents.
  • Full paths: only the folder name, and a one-way hash of the path.
  • Folders you ignore with /zest-ignore.

Where the data goes

To the Zest API at /api only, over HTTPS, with this plugin's own device token. The API checks it and stores it under your workspace. How Zest works · how the token is kept.

Besides Zest:

  • No analytics. It downloads its runtime from GitHub Releases on first use and fetches updates in the background; set ZEST_NO_PREFETCH=1 to stop the background fetch.

Pause, sign out, uninstall

Pause syncing

/zest-disable

Uploads stop; sessions keep queuing on your laptop (the oldest go once 500 are waiting) and upload when you turn sync back on with /zest-enable.

Ignore a folder

/zest-ignore

Run it in the folder. Sessions there and in its subfolders are no longer read; ones already queued still upload. /zest-unignore undoes it.

Sign out

/zest-logout

Revokes the token on the server, erases it from ~/.grok-zest/zest2-auth.json, removes the session hook and stops the daemon. The queue stays.

Uninstall

grok plugin uninstall zest

Sign out first, so the session hook goes too. Then delete ~/.grok-zest and ~/.zest/bin/grok.

Troubleshooting

Install fails with “Couldn't scan every marketplace”

Grok also lists Claude Code's Zest marketplace, and both plugins are named zest. Install with the marketplace pinned:

grok plugin install zest@zest-grok --trust

Sessions do not appear in Zest

Run /zest-status and look at hook health. /zest-login reinstalls the hook even when you are already signed in. The hook runs when a session starts, so start a new Grok session afterwards.