📈 GH Trending Explorer 🎲 Surprise me

← all repos

riozilla / hermes-proactive

git clone https://github.com/riozilla/hermes-proactive.git

A set of instructions and scheduled tasks to make Hermes more proactive, helpful, and better at getting things done without being asked.

—
stars, 24h
+74
stars, 7 days · #688
+74
stars, 30 days · #3,048
74
★ total · +74% this week
3
forks · 0 open issues

Star history starts 2026-10-20; the chart appears after the second daily snapshot.

LanguagePython
LicenseMIT
Created2026-10-18 (2d ago)
Last push2d ago
Watchers2
OwnerUser

Links

README excerpt
# Hermes Proactive
I put this together because I wanted my Hermes agent to do more without being asked every time. It was good at responding to prompts, but I wanted it to notice things, follow up on work we'd started, and get small tasks done on its own.
The goal isn't more reminders or daily summaries. It's an assistant that pays attention and actually helps move things forward.
For example, instead of telling me to prepare for a meeting, it could gather the background, draft some talking points, and let me know they're ready. It should do that sort of prep work on its own, but still ask before sending messages, spending money, or making important changes.
This repo contains the instructions, scheduled jobs, and setup notes for making Hermes work more like that. It's not a one-click install; you'll need to adapt it to your own setup and test it.
## Start here
1. Read the installation guide and authority/privacy boundaries.
2. Make this repository available to Hermes, then review and paste INSTALL-PROMPT.md. Reading this repository alone grants no authority to install or act.
3. Resolve the user's timezone, permissions, private delivery route, and existing jobs locally. Merge the SOUL additions, install the operating skill into a private profile, and enable only tested responsibilities.
Prefer one attachment? Use the generated complete playbook.
## Eight ongoing responsibilities
All times below are **proposed local-time examples**, not a disclosed user's schedule. `{{USER_TIMEZONE}}` must be resolved locally before installation. A scheduled evaluation is an opportunity to work, not a notification quota.
| Responsibility | Proposed schedule | Without a tested cheap gate | Useful output |
|---|---|---|---|
| Change radar | Every 10 minutes | Every 30 minutes | A prepared answer, resolved discrepancy, or actionable next step |
| Meeting/travel preflight | Hourly at :05, :20, :35, :50 | Hourly at :05 | A relevant preparation packet, refreshed for material changes |
| Daily preparation | 08:00 daily | Same | Up to two completed preparations, not just a to-do list |
| Progress worker | 10:10, 14:10, 18:10 daily | Same | One verified private work unit advancing an accepted outcome |
| Curiosity and connections | 11:45 and 17:45 daily | Same | At most one genuinely relevant discovery per day |
| Evening closure | 20:30 daily | Same | Reconciled commitments, useful preparation, compact durable memory |
| Coverage health | Hourly at :07 and :37 | Every two hours at :07 | Honest coverage status and a precise recovery step when needed |
| Weekly friction | Friday 15:00 | Same | One tested small improvement or approval-ready proposal |
Start with one proactive agent run at a time. The suggested shared ceiling is six non-urgent unsolicited messages per local day, normally one hour apart, with 23:00–07:00 quiet hours unless the user chooses otherwise. These are ceilings, not targets, and do not grant a spending budget.
## What is included
| Path | Purpose |
|-