A simple status widget for checking whether Hermes Agent is alive
When runs a personal knowledge system for weeks, the number of moving parts can grow quickly. This setup included a , Resend for email, a , four scheduled jobs, and a knowledge pipeline that sent pages into Mnemo.
The main need was not a full analytics dashboard, but one small screen that answered whether everything was working right now. The useful checks were whether the could be reached, whether the Resend key still worked, whether the last scheduled job succeeded, and whether the model had hit a 429 error in the past hour.
The target design was a phone home-screen widget with no install, a 60-second refresh, and color-coded status. The backend used FastAPI and uvicorn on a local address, kept a 45-second memory cache, ran `hermes cron list` and ` stats`, and read the Hermes log file at `/root/.hermes/logs/agent.log`.
Key points
- Use a single status screen when a setup has many connected parts.
- Track checks that matter immediately: bot access, email key health, last scheduled job, and recent 429 errors.
- A phone-friendly widget with color status and a 60-second refresh can be enough.
- The example checks Hermes through `hermes cron list`, ` stats`, and the log file.
- A 45-second memory cache helps avoid checking the same things too often.