Zest for VS Code
One click from the Marketplace — VS Code takes it from there.
Install
New to Zest? Create your account first. Free for 3 seats, no credit card.
Create a free account- 1
Install from VS Code Marketplace
Click the button below to open the extension page directly in VS Code.
Install in VS CodeAlso see on VS Code Marketplace
- 2
Reload if Prompted
VS Code may ask you to reload the window to activate the extension. Click "Reload Now" to finish.
Check it works
Click the Zest icon in the activity bar to open Zest Stats. Signed out, it offers Sign In: click it and finish in the browser. Signed in, Status shows your email next to “Signed in as” and “Sync: OK”, with the time of the last sync below.
What it captures
What it reads on your laptop
- GitHub Copilot Chat's session files in the editor's workspace storage (
chatSessions/) for the workspace you have open.
What it uploads
- Copilot Chat sessions, agent sessions included: your prompts, Copilot's replies, the model, and token counts where Copilot reports them. Tool calls as names and counts.
- Each session's title and its folder (
org/repofrom the git remote, or the folder name). - Not Claude Code or Codex running inside VS Code: each has its own Zest plugin. Zest Stats lists any it finds without one under “Missing from your standups”.
When it syncs
3 seconds after the editor starts, then every 15 seconds for two minutes, then every minute, and only when a chat changed. It reads chats from the last 7 days, or since you installed it.
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. Code reaches Zest only where it is written inside a reply.
- Images. They are counted, not sent.
- Everything, while
zest.remotePersistenceis off.
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 and a few usage events (installed, sync state changes, signed out) to PostHog at
us.i.posthog.com, with your user id, the editor and its version, and your operating system.
Pause, sign out, uninstall
Pause syncing
Run “Zest: Toggle Remote Persistence” from the Command Palette, or turn off zest.remotePersistence in Settings. Nothing uploads until you turn it back on.
Ignore a folder
The extension has no per-folder switch. Pause syncing while you work in a folder you want kept out.
Sign out
Run “Zest: Sign Out” from the Command Palette. It revokes the token on the server and erases it from the editor's secret storage.
Uninstall
Sign out first, then uninstall Zest from the Extensions view. The editor keeps an extension's stored state after an uninstall, so signing out is what removes the token.
Troubleshooting
Zest does not appear after installing
The extension needs VS Code 1.95 or later. Update VS Code, then reload the window.
Sync says “Paused — chat tracking unavailable”
Zest reads Copilot Chat and has found no sessions in this window yet. Open your project folder and start a Copilot Chat; the next sync picks it up. Using Claude Code or Codex here instead? This extension can't see them: each needs its own Zest plugin.
Sync says “Error — chat extraction failed”
Zest could not read the editor's chat storage. Open View → Output and choose Zest from the list to see why. The extension keeps retrying.
GitHub Copilot in Zest
GitHub Copilot metrics shows what Zest does with these sessions, per engineer and per team.