CapRover Operator
From its catalog listing
Read-only setup diagnostics and human-approved, state-bound immutable-image deployment for one owner-configured CapRover app, with durable uncertainty, replay refusal and dated operation cards for self-hosted projects.
Good to know before installing
contacts the configured CapRover HTTPS origin and optional fixed health endpoint; CapRover returns all app definitions in memory, while only the configured app's keyed fingerprint and sanitized evidence enter a private local ledger. Image startup may run migrations. HTTP alone does not prove the serving image; runtime task evidence is optional. No shell, telemetry, self-updater or automatic rollback. Apply requires fresh native human approval in in_process mode. Safeguards apply only to this plugin's caprover_apply workflow and ledger; independent terminal or execute_code actions, other plugins, direct API calls and external operators require their own access controls and approvals.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs (this one needs
CAPROVER_OPERATOR_TOKEN), then asks whether to turn it on.hermes plugins install caprover-operator - Said no? Turn it on later:
hermes plugins enable caprover-operator - 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
- Memory & notes
- Maintained by
- fmercurio (Community)
- Needs
CAPROVER_OPERATOR_TOKENAPI key- Adds tools
caprover_doctorcaprover_plancaprover_applycaprover_reconcilecaprover_status- Adds hooks
pre_tool_callpost_approval_response- Works on
- linux, macos
- Needs Hermes
- 0.22.6 or newer
- Version
- 0.3.1
- In the catalog
- 2026-11-07
Known issues (from its catalog listing)
- Apply requires an interactive native human approval and plugins.isolation set to in_process; unattended, smart and YOLO approval cannot authorize a deployment.
- Servers without supported runtime task evidence produce metadata/HTTP observation receipts rather than a verified serving-image rollout.
- Inline HTML cards require the assistant to emit the returned public preview directive; unsupported or remote surfaces retain JSON facts and may show a file attachment.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in memory & notes
New Hermes Agent updates every day on X. Follow @HermesWatcher