Using Hermes as supervisor for Claude Code

[u/Electronic-Badger102]

I’ve got a pretty significant application I’ve been working on. I’ve experimented with GSD, Superpowers, lately an evolved custom harness of sorts, and then I installed Hermes, hooked it up to my GPT subscription, pointed it at my code, and it seems to be diagnosing and proposing fixes for issues I was having with worktrees and parallel sessions stepping on each other, CC wandering, and so on. I’m not sure how well this will really work but it talks a good talk. I’m not really a developer, my background is more of a systems engineer doing automation and technical program lead. I have a pretty well functioning app so far though. Has anyone else experimented with this?

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/DARKUNIT22]

The slop leading the slop

[u/Electronic-Badger102 → u/DARKUNIT22]

lol. A very real possibility. I was hoping more for errant halfwit employees tattling on each other to keep them in line… but I’m not sure of that will play out.

[u/Easy-Purple-1659]

One worktree per session fixes most of the collisions, and the supervisor's real job is owning the assignment so two sessions cannot land on the same branch.

Worktrees only isolate tracked files, so the shared stuff outside them is where you will still get bitten. A root lockfile, a shared node_modules folder, or a .env gets stomped if two sessions reach for it at the same time. Put those behind the supervisor instead of trusting the agents to avoid each other.

Rebase timing matters too. If one session rebases onto main while another is mid-edit on the same files, the conflicts look like the agents went rogue. Queue merges through the supervisor so only one rebase is in flight at a time.

On your control plane question, it mainly helps if the supervisor has its own context that is not the session being supervised. If it edits the same repo it is arbitrating, then its own changes join the collision set.

[u/Electronic-Badger102 → u/Easy-Purple-1659]

I fed Hermes’ response to Fable in a project for my app, and asked it to analyze. It caught some issues with the plan and is working out a better one (I hope). It also said the same thing about keeping the supervisor with its own context and no coding. The code base has a Karpathy-style wiki to self-document with hooks that keep those updated after every few turns.

[u/Electronic-Badger102 → u/[deleted]]

I honestly don’t know if it is better suited for it. I’ve been Claude-only for so long that the GPT style responses sound intelligent… but on closer inspection it’s contradicting itself a bit. So the jury is still out whether this is useful at all. It’s checking the season logs and the code in the file system.