# Hermes Watchdog: Hermes Agent plugin

> Scheduled jobs break without telling you.

Canonical: https://hermeswatcher.com/plugins/hermes-watchdog  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/hermes-watchdog  
Last updated in catalog: 2026-11-17

Scheduled jobs break without telling you. A job fails at 3am, so Hermes Watchdog tries the fix that fits (retry it, restart what broke, or pause it), then checks whether the next run worked. You only hear about it when the fix didn't take. When a repair would be a guess it stops and hands the job to the agent - the recorded error and the run's output go with it - and the agent's answer lands in your chat; an incident it handed to you closes itself after 24 hours if nothing new comes in. Free, no API keys, one command to install.

## Good to know before installing

Reads this profile's local cron store, fires the failing job through Hermes's own cronjob tool or pauses it, and marks the core incident alerted or closed through core's own ack as it hands work over; check steps run only from a user-authored playbook file, with a minimal environment (PATH, HOME, LANG plus what that step names); it also writes its own ledger in plugin-data. Its opt-in demo creates, runs and then removes a no-agent cron job and writes an executable script (mode 0755) under $HERMES_HOME/scripts; if Hermes stops partway through, that job and script stay behind. Disclosure — reads this profile's local cron store, fires the failing job through Hermes's own cronjob tool or pauses it, and marks the core incident alerted or closed through core's own ack as it hands work over; pressing Done closes that incident for good, so the same error on that job stays silent afterwards. Check steps run only from a user-authored playbook file, with a minimal environment (PATH, HOME, LANG plus what that step names); it also writes its own ledger in plugin-data. Its synchronous rerun sets a private Hermes session flag that can change on any release. Its opt-in demo creates, runs and then removes a no-agent cron job and writes an executable script (mode 0755) under $HERMES_HOME/scripts; if Hermes stops partway through, that job and script stay behind.

From the plugin's catalog listing.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install hermes-watchdog
```

2. Said no? Turn it on later:

```bash
hermes plugins enable hermes-watchdog
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Automation & multi-agent, Chat apps & voice
- Maintained by: 33hodl (Community)
- Needs: No API keys declared
- Adds tools: `watchdog_status`, `watchdog_repair`, `watchdog_runbooks`
- Requires Hermes: `>=0.22`
- Version: 0.10.1
- In the catalog since: 2026-11-17

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/hermes-watchdog)
- [Source code](https://github.com/33hodl/hermes-watchdog#readme)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt
