Grok Build
Add the marketplace, install with --trust, and log in.
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
- 1
Add the Marketplace
In a terminal, add the official Zest marketplace for Grok Build:
grok plugin marketplace add Winding-Labs/zest-grok - 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
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
Authenticate with Zest
Inside a Grok session run the Zest login command. Do not use Grok's built-in /login — that is xAI auth.
/zest_login - 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_statusWhat it records
- Each Grok Build session transcript: your prompts, Grok's replies, the tools it called, the model and per-turn token counts.
- The folder each session runs in.
- Sessions queue locally and sync in the background once you are signed in, so nothing is lost offline.
What it never sends
- Secrets. The same redaction every Zest plugin uses runs before anything leaves your machine.
- Folders you exclude with
/zest_ignore./zest_disablestops uploads; sessions still queue locally.
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 --trustSessions 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.