Failed deploys, unhealthy apps, env changes and commits not deployed yet, and servers under pressure, in one list. The page, the status-bar chip, the agent and the alert job all read that list.
Every action asks first
Deploy, restart, stop or roll back from the page or from the chat. The agent's actions wait for your approval, and runs where no one can answer are refused before any request reaches Coolify.
Failed deploys, explained
Paste a failed log and Hermes classifies it against a catalogue of eleven common self-hosting failures, with the evidence lines and a likely fix. The classifier is plain pattern matching, no model call.
Your layout, edited by you or Hermes
Start from a preset, rearrange the widgets in the page, or ask Hermes to do it. The page and the agent edit the same layout, and a save that collides with a newer one is refused, not lost.
Safe by design
What it touches
Your Coolify instance, through the API token you give it. The token is the permission model.
Your apps' git hosts, to see commits that are not deployed yet.
Its own data folder in your Hermes profile.
What asks first
Every deploy, restart, start, stop, cancel and rollback the agent wants to run.
Protected environments (production by default) are refused for the agent unless you allow them.
What leaves your machine
Requests go to your Coolify, Coolify's public release feed and your apps' git hosts. Tool results reach your model provider like any tool result. No telemetry.
Disclosures, as written in the README
Also
The plugin talks to the Coolify instance you configure, to Coolify's public release feed, and to the git hosts of your applications' repositories for "branch ahead". It calls nothing else.
Also
Tool output names a token only by its role and the first 8 hex digits of its SHA-256. Any token stored for Hermes is readable by whatever else runs as Hermes on that host, so give each token only the rights it needs.
Also
Every agent call goes through Hermes' approval prompt; unattended runs refuse without any request. On a protected environment the agent is refused unless you switched that on.
Also
The page's route acts on your click without a Hermes prompt, so anything on the host that can call Hermes' local API as you can call it too. Give the API token only the projects you would let that touch.
Also
Log text is untrusted: secrets matching known formats are masked first. Masking covers known formats only, so the log lines that are shown can still reach your model provider.
Also
No telemetry or analytics, no inbound port, no background process of its own.
In Coolify, turn on API access and create an API token with read and deploy on all projects.
3
In Hermes Desktop, open Coolify Cockpit in the sidebar and enter your Coolify URL and the token.
Questions
What do I need?
Hermes 0.23.0 or newer and a Coolify instance that the machine running the Hermes backend can reach, with API access turned on.
Which token should I create?
One API token with read and deploy on all projects. A read-only token gives a read-only cockpit. Leave read:sensitive off: it lets a token read deployment logs and secret values.
Does it work without Hermes Desktop?
Yes. The tools work in any Hermes chat, and hermes coolify-cockpit alerts on starts an alert job that runs without Desktop. The Cockpit page and the status-bar chip need Desktop.
What leaves my machine?
Requests to your Coolify, to Coolify's release feed at most every 6 hours, and to your apps' git hosts. What the tools read reaches your model provider. There is no telemetry.
Can the agent touch production?
Not by default. Environments in protected_environments (production by default) are refused for the agent. Your own buttons work there, with a confirmation that names the environment.
How do I update?
Run hermes plugins update coolify-cockpit, then start a new chat. On a server, update there and on the Desktop computer, then switch Agent in <profile> off and on in Capabilities → Plugins.
How do I uninstall?
Run hermes coolify-cockpit alerts off if you turned alerts on, then hermes plugins remove coolify-cockpit.
What licence is it under, and where do I get help?
MIT. Open an issue on GitHub and include what coolify_capabilities reports, never a token.
Build it with us
Coolify Cockpit is open source under MIT. Issues, ideas and pull requests are welcome on GitHub.
