Zest for Claude Code
Track every Claude Code session, across every project on your machine.
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
Add the Marketplace
No Node.js needed: the plugin runs its own binary. Open Claude Code and run the following command:
/plugin marketplace add https://github.com/Winding-Labs/zest-claude - 2
Install the Plugin
Run the command below. When Claude Code asks where to install, choose "User" scope so Zest tracks your sessions across every project (not just this one).
/plugin install zest - 3
Reload Plugins
Load the newly installed plugin so its commands are available. Run this before logging in:
/reload-plugins - 4
Authenticate with Zest
Authenticate your Claude Code instance with Zest. This also auto-configures the status line to show sync errors, plugin updates, and dev mode at the bottom of Claude Code:
/zest:login - 5
Start Coding!
The plugin works automatically in the background. You're all set!
Check it works
Run the status command in Claude Code. It shows your account and workspace, what synced in the last hour, what is still queued, whether the sync daemon is running, and whether this folder is tracked.
/zest:status What it captures
What it reads on your laptop
- Claude Code's session transcripts in
~/.claude/projects/(or underCLAUDE_CONFIG_DIR), subagents' included. - Your plan and billing mode from
~/.claude.json, and the model, context use and rate limits Claude Code reports to its status line.
What it uploads
- Your prompts and Claude's replies: their text only. A skill you run appears as
[Skill: name]with its arguments. - Each reply's model and token counts (input, output and cache), and the git branch it ran on.
- How many times each tool, skill, subagent and MCP server was used, and how many images, as counts.
- The branch, commit SHA and PR URL when Claude runs
git commitorgh pr create, so a session links to its pull request. - The session's title (the first 100 characters of its first prompt), start time and folder: the repo's
org/repofrom its git remote, or the folder name.
When it syncs
Hooks read each session while Claude Code works (after tool calls, and when the session ends) into ~/.claude-zest/queue/. A background process uploads the queue every 60 seconds and exits 5 minutes after the last Claude Code session closes. A session uploads once it has 3 messages. Nothing is read while you are signed out; your first sign-in imports up to 10 of today's sessions if your account has none yet.
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.
- Code diffs and file contents. Zest never reads what Claude's tools write, and never sends a tool's input or output.
- Thinking blocks and images.
- Built-in slash commands and
/zest:*commands, and Claude's answers to them. - Full paths: only the folder name or
org/repo, and a one-way hash of the path. - Anything, if redaction cannot start.
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:
- Error reports to PostHog at
us.i.posthog.com, with the plugin, Node and operating system versions, your user id, email and workspace, and for some errors the project's path; plus one event when you sign in. - GitHub Releases, to download the plugin's own binary, which it checks against its SHA-256.
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 ~/.claude-zest/zest2-auth.json and stops the background process. The queue stays.
Uninstall
/plugin uninstall zest Then delete ~/.claude-zest and ~/.zest/bin/claude, and remove the statusLine entry Zest added to ~/.claude/settings.json.
Troubleshooting
Adding the marketplace fails with “git not found”
Claude Code clones the GitHub marketplace with git, which a Windows PC often lacks. Add the same marketplace from one file instead, which needs no git: /plugin marketplace add https://meetzest.com/setup/claude-code/marketplace.json, then /plugin install zest.
/zest:login is not recognized
The plugin is not loaded yet. Run /reload-plugins; if the command is still missing, reinstall the plugin.
Only one project shows up in Zest
The plugin was installed at Project or Local scope, which limits it to one repository. Uninstall it and run /plugin install zest again, choosing User scope.
Sessions are not syncing
Run /zest:status. If the daemon is not running, start a new Claude Code session. /zest:sync uploads the queue now; the daily logs in ~/.claude-zest/logs/ show what failed.
Updating the plugin
- 1
Open Plugin Manager
Open the plugin manager by running:
/plugins - 2
Select Zest
Navigate to "Installed" and select the Zest plugin.
- 3
Update the Plugin
Choose "Update Plugin" from the options.
- 4
Restart Plugins
Apply the update by running:
/reload-plugins
Claude Code in Zest
Claude Code analytics shows what Zest does with these sessions, per engineer and per team.