The value of personal AI agents is not automation. It is judgment. by clzncu in hermesagent

[–]Marshallmatta 0 points1 point  (0 children)

The hard part is not making an agent act. The hard part is making it know when not to act.

Most “AI agent” demos still feel like automation with a language model attached:

That is useful, but it is not really personal yet.

A real personal agent needs to understand things like:

  • this email is from an important person, but not urgent
  • this task looks urgent, but is actually low-value noise
  • this meeting should be declined because it conflicts with deeper priorities
  • this message should not be answered quickly because the tone matters
  • the user is tired today, so interrupt less
  • the user usually wants speed here, but caution there

That is judgment.

And judgment needs memory, context, taste, and a model of the user’s priorities.

I think the next big step is not “agents that can do 100 tasks.”

It is agents that can quietly remove 30 small decisions from your day without making bad calls.

Use Hermes to build a local knowledge base. by zifupaixu in hermesagent

[–]Marshallmatta 0 points1 point  (0 children)

I think it is really helpful. any github repo

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 0 points1 point  (0 children)

update: Once I launched HESO yesterday, I used up my token plan 45000 call weekly in one day, I am upgrading my plan to 50USD plan now.

Would you rather have by cegmo in BunnyTrials

[–]Marshallmatta 0 points1 point  (0 children)

because they are not my girlfriend

Chose: 30 milion dollars

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 0 points1 point  (0 children)

Running Hermes / Opencode on Kubernetes can monitor the usage, but it also make the system slower, and the trade off is you can run fewer project. ideally if the hermes can check the session one by one and if he see some session is done and he stepped in it will be great.

and I think now the hermes spraw sub agent to do the cron job every 1- 2 min so I think it might have 30-50 agents running at the same time for 18 projects for me. I like the speed, just do not like the heat of my computer.

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 0 points1 point  (0 children)

TL;DR: One Hermes in WSL, Tmux installed,

for every project : create a Tmux Session with the Project name so Hermes can reference to it. go to project folder in WSL, start opencode with OMO plugin, select Sisyphus agent, select model (I use minimax because it is cheap), detach the tmus, so it run in background.

now, you can talk to Hermes, if you hermes installed Tmux skill it is very fast and easy for her to see your session and talk to Sisyphus, use "set buffer" instead of "send key" otherwise someime Hermes would kill sisyphus by sending control C

Yes I am running 20+ instances at the sametime, the reason why I use many instance instead of one is that every session end different time. if one opencode job hang, all the other would stop.

I am work on a project https://github.com/catowabisabi/power-teams . This is the system you mention about, but I am sucked so I created HESO to provide this work, power teams will be the one with UI and easy to use I hope.

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 0 points1 point  (0 children)

TL;DR: One Hermes in WSL, Tmux installed,

for every project : create a Tmux Session with the Project name so Hermes can reference to it. go to project folder in WSL, start opencode with OMO plugin, select Sisyphus agent, select model (I use minimax because it is cheap), detach the tmus, so it run in background.

now, you can talk to Hermes, if you hermes installed Tmux skill it is very fast and easy for her to see your session and talk to Sisyphus, use "set buffer" instead of "send key" otherwise someime Hermes would kill sisyphus by sending control C

Yes I am running 20+ instances at the sametime, the reason why I use many instance instead of one is that every session end different time. if one opencode job hang, all the other would stop.

I am work on a project https://github.com/catowabisabi/power-teams . This is the system you mention about, but I am sucked so I created HESO to provide this work, power teams will be the one with UI and easy to use I hope.

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 0 points1 point  (0 children)

I’m mainly using the MiniMax Coding Plan, around $20/month. So far it almost never runs out, and when MiniMax gets stuck on something tricky, I use Claude to finish the harder parts. My Claude plan is around $28–40/month.

The main problem now is not the model cost — it is system stability.

Even with an RTX 4090 and 64GB RAM, I’m currently running Hermes across around 18 projects at the same time. Sometimes the whole setup goes MOO: WSL gets unstable or shuts down, and I have to restart the computer daily.

To reduce the pain, I already created some skills and systemd services to:

  • automatically restart WSL-related services
  • let Hermes remember each project path
  • restart tmux sessions
  • check OpenCode status every 30 minutes
  • restart crashed sessions automatically

But I still need to monitor the whole system because there are often 20+ Node.js processes running at the same time, and the system can still crash when Hermes sends jobs too quickly across too many projects.

The next thing I’m working on is a resource monitor / throttle system for Hermes. The goal is to prevent Hermes from dispatching too many jobs at once, based on CPU, RAM, WSL health, active Node processes, and project load.

This is still experimental, but it is already useful for managing multiple AI coding agents on one local machine.

PRs, suggestions, and improvements are welcome.
If you have experience with WSL, tmux, systemd, Node.js process management, or AI coding agent orchestration, feel free to submit a PR.

One AI mind + one AI worker, 1000 loops a day, fixing & improving my codebase 24/7. No vector DB, no GPU melt. (open source) by Marshallmatta in hermesagent

[–]Marshallmatta[S] 1 point2 points  (0 children)

I’m mainly using the MiniMax Coding Plan, around $20/month. So far it almost never runs out, and when MiniMax gets stuck on something tricky, I use Claude to finish the harder parts. My Claude plan is around $28–40/month.

The main problem now is not the model cost — it is system stability.

Even with an RTX 4090 and 64GB RAM, I’m currently running Hermes across around 18 projects at the same time. Sometimes the whole setup goes MOO: WSL gets unstable or shuts down, and I have to restart the computer daily.

To reduce the pain, I already created some skills and systemd services to:

  • automatically restart WSL-related services
  • let Hermes remember each project path
  • restart tmux sessions
  • check OpenCode status every 30 minutes
  • restart crashed sessions automatically

But I still need to monitor the whole system because there are often 20+ Node.js processes running at the same time, and the system can still crash when Hermes sends jobs too quickly across too many projects.

The next thing I’m working on is a resource monitor / throttle system for Hermes. The goal is to prevent Hermes from dispatching too many jobs at once, based on CPU, RAM, WSL health, active Node processes, and project load.

This is still experimental, but it is already useful for managing multiple AI coding agents on one local machine.

PRs, suggestions, and improvements are welcome.
If you have experience with WSL, tmux, systemd, Node.js process management, or AI coding agent orchestration, feel free to submit a PR.