Zest
Docs / One-command install

One-command install

One command finds the coding agents on your machine, installs the Zest plugin for each, and signs them all in with one browser approval.

Run it

In a terminal, with Node.js 18 or later:

npx @winding-labs/zest
  1. It opens your browser. Sign in to Zest there; there is no code to type. No browser on that computer? Open the link it prints and type its code.
  2. It sets up every agent it finds on your machine, with no list to pick from: Claude Code , Codex , Grok Build , Hermes , OpenCode , Freebuff .
  3. For each one it runs that agent's own install commands, the same ones its page gives, and signs the plugin in from your one sign-in. One that fails gets its manual steps printed.
  4. It ends with the everyday commands: open Zest, check your agents with zest verify, and remove it all with zest install --uninstall.

Cursor and VS Code are not set up here: the extension signs in from the editor (Cursor, VS Code). Codex runs the plugin's hooks only once you trust them in /hooks, and the installer reminds you.

What it changes on your machine

  • The zest binary, downloaded from GitHub Releases and checked against the SHA-256 that ships in the npm package, in ~/.zest/bin/, linked from ~/.local/bin/zest. On Windows it is %USERPROFILE%\.zest\bin\zest.exe, with that folder added to your own PATH.
  • The Zest plugin for each agent it found, installed by that agent's own commands.
  • One sign-in token per plugin, in that plugin's zest2-auth.json, plus the installer's own in ~/.zest/collector/. A plugin that is already signed in is left alone. How tokens are kept.

What it sends

  • To Zest: the device sign-in, then one request that makes a token for each plugin, within 10 minutes of your approval.
  • To PostHog: “CLI Install Started” and “CLI Install Completed”, under an anonymous id for the install that is never tied to your account. Nothing is sent with DO_NOT_TRACK=1, ZEST_TELEMETRY=0 or CI=true, on a dry run, or when you uninstall.
  • Your sessions are sent by the plugins, not the installer. Each plugin's page says what.

Options

  • --yes installs the agents it found without asking.
  • --only=claude,grok limits it to the agents you name.
  • --dry-run only reports what it would do.

Undo it

npx @winding-labs/zest --uninstall

It takes the Zest plugin off every agent it finds, with each agent’s own command, and signs them all out. Then it stops the collector, removes the hooks and shims the collector added and removes the binary. Add --only=claude,grok to take Zest off just those agents and keep the rest.

The collector (beta)

The installer can also collect Claude Code and Codex sessions itself, in place of their plugins. It is off: zest enable turns it on for one agent, and only for an account Zest has opted in to the beta. Until then nothing about it runs, and the plugins collect as their pages describe.