Aftercare

From its catalog listing
Your agent checks its own work after the fact. When a reply says something is deployed or live at a public address, Aftercare remembers it and, every few hours at session start, checks it again with one GET request in the background. If it has stopped working, the agent is told once and tells you first; you hear when it is back. /aftercare lists and checks, and hermes aftercare check runs from cron. Never checks private networks or runs commands.
Good to know before installing
on by default, sends background GET requests (user agent `hermes-aftercare/0.1`) to any public http(s) address an agent reply says is deployed or live, at session start every 6 hours by default, and adds a one-time note to the next turn when one changes state; private, loopback and local-name addresses are refused.
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 aftercare - Said no? Turn it on later:
hermes plugins enable aftercare - 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
- Automation & multi-agent
- Maintained by
- salch-cred (Community)
- Needs
- No API keys declared
- Adds hooks
post_llm_callon_session_startpre_llm_call- Needs Hermes
- 0.23 or newer
- Version
- 0.1.0
- In the catalog
- 2026-11-10, updated 2026-11-18
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in automation & multi-agent
All automation & multi-agent plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher