Zest
Docs / OpenCode

Zest for OpenCode

Install the plugin into opencode and log in.

OpenCode logo

Works with opencode 2.x (@opencode/cli) and 1.18 or newer (opencode-ai) — opencode --version tells you which you have. opencode loads plugins when it starts, so restart it after installing; on 1.x the first start after any plugin install can take about a minute. Capture runs inside opencode after every finished turn — there is no hook file or extra process.

Install

New to Zest? Step 3 opens your browser, where you can create your account. Free for 3 seats, no credit card.

Create a free account
  1. 1

    Install on opencode 2.x

    Add Zest in a terminal, then run opencode service restart so the background service loads it. opencode checks for plugin updates daily; opencode plugin update applies them.

    opencode plugin add github:Winding-Labs/zest-opencode
  2. 2

    Install on opencode 1.x

    Add Zest to your global opencode config. -g covers the TUI, opencode run and opencode serve.

    opencode plugin zest-opencode@github:Winding-Labs/zest-opencode -g

    To update on 1.x, run the same command with the release tag and -f, …zest-opencode#vX.Y.Z -g -f. 1.x never refetches a plugin it has already installed.

  3. 3

    Authenticate with Zest

    Start opencode, then type the Zest login command in the chat. It answers at once with a link and a code; approve them in your browser and the sign-in finishes in the background. /zest-status shows when it has.

    /zest-login
  4. 4

    Start coding

    The plugin captures every opencode session when a turn finishes. /zest-status shows auth and sync.

Check it works

Type the status command in the opencode chat. It shows your account and workspace and what has synced.

/zest-status

What it captures

What it reads on your laptop

  • The sessions opencode keeps, through opencode's own plugin interface. No files and no hook.

What it uploads

  • Your prompts and the replies, subagents' included. Files you attach and tools the agent calls appear as [file: name] and [tool: name], never their contents.
  • Each session's title, start time, folder name, model and provider, and token counts.

When it syncs

Inside opencode: when a session goes idle (1.x) or a run ends (2.x), the plugin reads it and uploads, and a 60-second timer sends anything left. It reads the whole conversation, messages from before you installed included, once a workspace is selected. On 1.x your first sign-in imports up to 10 of today's sessions.

What stays on your laptop

  • Secrets. Every text field is checked against 74 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.
  • Reasoning, tool inputs and output, file contents and diffs.
  • Your /zest-* commands.
  • Full paths: only the folder name, and a one-way hash of the path.
  • Folders you ignore with /zest-ignore.

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.
  • opencode shows a command's answer through your model, so what /zest-status prints (your email and workspace) reaches your model provider.

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

Sessions in this folder and 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 and erases it from ~/.opencode-zest/zest2-auth.json. The queue stays.

Uninstall

Remove the Zest entry from the plugin list in your opencode config (~/.config/opencode/opencode.json), restart opencode, then delete ~/.opencode-zest.

Troubleshooting

/zest-login printed a link and nothing else

That is how it works: approve the code in your browser and the sign-in finishes in the background. Run /zest-status to see it.

/zest-status

The Zest commands are missing

opencode loads plugins when it starts. Restart it; on 2.x run opencode service restart too.