Workbench Link
From its catalog listing
Route Hermes native file, terminal and code tools to one explicitly selected Linux/Docker project worker.
Good to know before installing
when `terminal.backend: workbench_link` is selected, terminal, file and code-execution commands and their output are sent over HMAC-authenticated HTTPS to a project worker you start and bind, which runs them in a network-less, read-only Docker container with your project directory mounted read-write; `hermes workbench-link serve` opens a TCP listener (127.0.0.1:8765 by default, any address you pass with --listen) and keeps a ledger of commands' retained output under the plugin data folder.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install workbench-link - Said no? Turn it on later:
hermes plugins enable workbench-link - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Coding & developer tools
- Maintained by
- dotmantissa (Community)
- Needs
- No API keys declared
- Adds hooks
pre_tool_call- Works on
- linux
- Needs Hermes
- 0.23.0 or newer, below 0.24.0
- Version
- 0.1.0
- In the catalog
- 2026-11-10
Known issues (from its catalog listing)
- Requires plugins.isolation=in_process, one foreground CLI session per profile, and explicit broker/worker startup.
- Linux/Docker worker only; gateway multiplexing, PTY/background stdin and persist_on_release are unsupported.
- Physical WAN behavior and live-model conversations have not been verified.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in coding & developer tools
All coding & developer tools plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher