Hermes does the routines after he says yes
u/xbxz let Hermes take pull requests, status and builds in a small software company, after a yes. Local models on 16 GB looped. v41 flash was the one that was good enough. He scores it 8/10. The Slack session is unsolved.
Done with HermesAdvanced
What was done
On 17 September 2026 u/xbxz writes that he runs a small software company with about 20 developers across 4-5 client systems. Every day the team reviews large pull requests, stated as 5k+ and 1k-. Prototypes, review, daily status and ios and apk builds for clients were manual work. He tried Hermes with a couple of local models on 16 GB of vram. The agent looped on tool calls. Deepseek v4 flash was somewhat better, but not what he was looking for. v41 flash was good. Then he put full Hermes on one vps. He gave it root, access to the team's IRC, the repo, Cloudflare and nginx, and let it act after he says yes to the question it asks. After a couple of days of tweaking it does most of the manual tasks he listed. Now he creates a skill first, adds test cases and then does the actual task. He misses a test that shows which skill a prompt will pick. He has not found a way from the CLI to Slack without corrupting the sqlite database. He has raised a couple of issues with suggested fixes on the hermes git. It uses a lot of tokens. Overall he scores it 8/10.
How it went
After the tweaking, Hermes does most of the tasks he listed, and only after a yes. The CLI session cannot be continued into Slack without touching the database, as he describes it.
Worth knowing
He does not name a pull request, a client or a build that was delivered. About 20 and 4-5 are his own figures. Root is what he gave, not something you need to repeat. The score of 8/10 is his.
How to do it
- Create a skill for one task, and add test cases before it runs.
- Ask it to show what it will do to the repo, and wait for a yes.
- Keep the CLI session and Slack apart until you know the database can take the switch.
Try it with Hermes
Create a skill for [task] in [repo] and add test cases. Show what you will change. Do not deploy, do not change the server and do not send a notice until I say yes.
Replace text in brackets with your own.
Done when. The tests have been run, the diff has been read, and nothing has been deployed without a yes.
Safety rule. No deploy and no notices until you have said yes.
Read the original
Read the original · u/xbxz on Reddit ·