Zest for Hermes
One command to install, one to log in.
Alpha: The Hermes plugin is under active development and you may encounter bugs. It currently installs via the Hermes plugin CLI — no additional setup is needed beyond authentication.
Install
New to Zest? Step 2 opens your browser, where you can create your account. Free for 3 seats, no credit card.
Create a free account- 1
Install the plugin
Run the following command to install and enable the Zest plugin for Hermes.
hermes plugins install https://github.com/Winding-Labs/zest-hermes --enable - 2
Authenticate with Zest
Inside any Hermes session, run the login command. It will open a browser window for authentication.
/zest_login - 3
Start coding
The plugin runs in the background and automatically tracks your Hermes sessions. No additional configuration needed.
Check it works
Inside a Hermes session, run the status command. It shows the account you are signed in as, your workspace, what synced in the last hour, what is still pending, whether the background daemon is running, and the plugin version, with the update command when a newer one is out.
/zest_status What it captures
What it reads on your laptop
- Hermes's own database,
~/.hermes/state.db, read-only, starting from the newest message when the plugin first runs. - The size and entry counts of your Hermes memory and user notes, and how many skills you have. Not their text.
What it uploads
- Your messages and Hermes's replies, as Hermes stores them. A reply that only calls tools is sent as
[tool: name], with tool names only. - Each session's title, start and end, duration, model, token counts (cache and reasoning included) and the cost Hermes reports for API-billed sessions.
- How many times each tool and skill was used, and the memory and skill changes the agent made.
When it syncs
After each turn the plugin reads the new messages, and a background daemon uploads every 30 seconds. A session uploads once it has 3 messages (1 in agent mode). Turns from while you are signed out are read after you sign in. The daemon stops about 90 seconds after the last Hermes session closes.
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.
- Messages from before the plugin was installed. A session you continue sends its totals, not its earlier messages.
- Tool and system messages, diffs and file contents.
- Any folder or path.
- Sessions you ignore with
/zest_ignore. Turns skipped while a session is ignored are never sent later. - Anything, if redaction cannot start: the daemon stops instead.
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; plus one event when you sign in.
Pause, sign out, uninstall
Pause syncing
/zest_disable Uploads stop; sessions keep queuing on your laptop, with no limit, and upload when you turn sync back on with /zest_enable.
Ignore a session
/zest_ignore Stops reading the current session. /zest_unignore undoes it; /zest_list_ignored lists them.
Sign out
/zest_logout Revokes the token on the server, erases it from ~/.hermes-zest/zest2-auth.json and stops the daemon. The queue stays.
Uninstall
hermes plugins remove zest-hermes Then delete ~/.hermes-zest.
Troubleshooting
The plugin does not load
Run hermes plugins list to check that zest-hermes is installed and enabled. If it is disabled, enable it:
hermes plugins enable zest-hermes Signed in to the wrong account
/zest_status shows which account is signed in. Run /zest_logout, then /zest_login. Sessions queued under another account sync only after you sign back in as that account.
A session has not synced
A session syncs once it has at least 3 messages, and /zest_status counts the ones still waiting. /zest_sync uploads the queue now.