Docs / Introduction

Introduction to Zest

Zest is AI coding analytics for engineering teams: it shows which coding agents, models and skills each engineer uses, what they cost, and which sessions end in merged pull requests.

Get started

  1. 1

    Install a plugin. A few commands in your coding agent, or one click in Cursor or VS Code.

  2. 2

    Code like normal. Nothing changes about how you work.

  3. 3

    Check the dashboard tomorrow. Your first sessions will be scored.

Free for 3 seats. No credit card.Starter covers 3 seats. Start freeGet started or jump to plugins.

Who Zest is for

Zest is for engineering teams whose engineers use coding agents and keep their code on GitHub, from one engineer up. Each vendor's own dashboard covers its own agent; Zest puts every agent's sessions next to the pull requests they led to.

It can't help a team without coding agents, since its data comes from their sessions, or a team whose code is on GitLab, Bitbucket, Azure DevOps or self-hosted Git. There is no on-premises install, and Zest doesn't do time tracking, developer surveys, DORA metrics or finance reports.

How it works

  • Capture — The plugin records each agent session locally: prompts, model, skills, tool calls, duration.

  • Redact — Secrets and sensitive strings are stripped on your machine, before anything is sent.

  • Sync — Sanitized sessions upload to your workspace in the background.

  • Analyze — Zest scores each session and links it to the pull request it produced.

  • Share — The dashboard, standups and CheatCodes push what worked back to the team.

You never write anything down. The plugin is the only setup step.

What Zest measures

  • AI time

    An estimate of the time your agents spent working, per engineer. It is not working hours.

  • Models and harnesses

    Which ones your team actually reaches for.

  • Prompts and skills

    The planning prompts behind your best sessions.

  • PR throughput

    Sessions tied to merged pull requests, via the GitHub integration.

Per engineer, per team, over time — so a practice that works for one person stops living in one person's head.

Plugins

Install as many as you use. Sessions from every agent land in the same workspace.

Install a Zest plugin

Paste these in your terminal, in any repo.

Add the marketplace

/plugin marketplace add https://github.com/Winding-Labs/zest-claude

Install the plugin

/plugin install zest

Reload plugins

/reload-plugins

Authenticate with Zest

/zest:login

Your code stays yours

  • Redaction runs locally, before upload.

  • /zest:ignore turns tracking off for a folder.

  • /zest:privacy shows exactly what gets redacted.

  • /zest:disable stops syncing entirely.

At a glance

Here is what most teams ask about before they install.

  • Coding agents — Claude Code, Codex, Cursor, VS Code with GitHub Copilot Chat, Hermes, Grok Build, OpenCode and Freebuff.

  • Code host — GitHub only, through the Zest GitHub App.

  • Uploaded — Each session's prompts, replies, model, token counts, skills and tool names, after secrets are redacted on the machine. Tool inputs and outputs stay on the machine.

  • Not uploaded — Code diffs.

  • Retention — Session text and GitHub events are kept 90 days by default and at most; the workspace owner can choose 12 hours or 1, 7, 30 or 90 days.

  • Plans — Starter is free (3 seats, no credit card). Pro is $49 a month with 5 seats and Max is $149 a month with 10 seats — priced per workspace, not per engineer, with extra seats at $19 a month.

Before you install

Does Zest upload our source code?

No code diffs are collected. The plugins do upload each session's prompts and replies, along with its metadata, after redacting secrets on the engineer's machine.

Who controls what gets collected?

The workspace owner can stop collecting prompts, replies or GitHub events and set how long data is kept. An engineer can only tighten their own settings.

Is there a free plan?

Yes. Every workspace starts on Starter, free for 3 seats with no time limit and no credit card, and can switch to Pro or Max from Billing.

What does setup involve?

An admin installs the Zest GitHub App and picks repositories. Each engineer then installs the plugin or extension in their agent and logs in.

Next

  • Ask Zest — Ask your own data a question in plain English.

  • Standups — Written from the day's sessions and pull requests, not memory.

  • CheatCodes — The prompts and skills your teammates keep reusing.

Create a workspace