Zest logo Zest
Docs / Cursor

Cursor

One click from the Open VSX Registry — Cursor takes it from there.

Cursor logo

Install

  1. 1

    Install from Open VSX Registry

    Click the button below to open the extension page directly in Cursor.

    Install in Cursor

    Also see on Open VSX Registry

  2. 2

    Reload if Prompted

    Cursor may ask you to reload the window to activate the extension. Click "Reload Now" to finish.

Check it works

Open the Zest view from the side bar; its icon sits in the icon row with Explorer and Search. 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. The extension syncs every minute. If you also run Claude Code or Codex, the view lists them under “Missing from your standups” until their own Zest plugin is installed.

What it records

  • Cursor's chat and agent sessions in the project you have open: your prompts, the replies, the model and the tools the agent called.
  • Token counts and cost, only if you switch them on. Cursor does not save real token counts locally, so the Zest view's Settings has a “Cursor Dashboard API” switch that reads them from Cursor's usage dashboard with your Cursor sign-in. It is off by default.

What it never sends

  • API keys, passwords and tokens. Redaction is on by default and runs on your machine before upload.
  • Anything at all until you are on a team in a Zest workspace. With no team, sync stays paused.
  • Your messages, the assistant's replies, or both, if a workspace admin turns that collection off.
  • Everything, if you turn off zest.remotePersistence in Settings.

Troubleshooting

Sync says “Paused — chat tracking unavailable”

Zest has found no Cursor chats in this window yet. Open your project folder and start a chat or agent session; the next sync picks it up.

Sync says “Paused — no team assignment”

You are not on a team in any Zest workspace, so there is nowhere to sync to. Ask a workspace admin to add you to a team; sync resumes by itself.

Sync says “Error — chat extraction failed”

Zest could not read Cursor's chat storage. Open View → Output and choose Zest from the list to see why. The extension keeps retrying.

Cursor in Zest

Cursor analytics shows what Zest does with these sessions, per engineer and per team.