Incident Scribe Agent with Hermes
Hermes runs on Nous Research's open models, and the work here is plain language under time pressure: turn an alert about a 5xx ratio into one sentence somebody in support can read. That is comprehension and phrasing rather than code generation. Everything it says has to come from the incident, the alerts, the past incidents and your runbook notes.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
P1: Checkout API error rate 11% for 6 minutes
TriggeredMonitor checkout-api 5xx ratio triggered at 14:02 UTC against a 2% threshold, currently 11.4%, with 340 of the last 2,980 requests returning 502 from the payments upstream. Two alerts merged into this incident, both from eu-west-1. Escalation policy Payments Primary, nobody has acknowledged yet.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect PagerDuty
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Runbook notes
What your team needs said about each service - what it does, who feels it when it breaks, and any standing context you want repeated in an update.
Comms style
How your incident updates should read and how often - the tone, who is reading, and the cadence that sets the next update time, for example every 30 minutes while a P1 is open.
Runs on Hermes
Preselected for this page — connect your Hermes account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Hermes for this agent
Alert into plain English
The opening line has to be readable by someone who has never heard of the service, and that translation is the reasoning this harness contributes.
Nothing beyond the data
No cause, no ETA and no customer count appears unless the incident or your notes actually contain it.
Before you fork
Will an open model stay calm in its wording?
Tone comes from the comms style you write, so tell it who is reading and how a P1 should sound to them. Rehearse the staged live outage first, since that is where an update can drift from factual into dramatic. What it cannot do in any tone is state a cause or an ETA nobody gave it.
Run it with a different agent
Put Incident Scribe Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.