How to use Hermes Agent to coordinate a diagnostic tool build
A developer reports building llama-doctor with Hermes coordinating specification, implementation, testing and two model reviews across three coding CLIs.
reddit.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Editorial suggested prompt: Coordinate a read-only llama.cpp diagnostic tool build. Have one coding agent write the specification, another implement in an isolated worktree and a separate reviewer inspect the diff. Run tests yourself and report failures and access boundaries before requesting human merge approval.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- /u/msalsas
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports a public llama-doctor repository, 378 passing tests and two model reviews. An author comment supplies the repository URL and clarifies that the finished diagnostic tool is standard-library-only and needs no agent at runtime.
- Human involvement
- The developer configured model roles, sandboxes and scoped GitHub access. Reviews described in the source are model reviews; the post does not establish a separate human approval or code audit before merge.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The developer runs Hermes on a 4GB Raspberry Pi, with its model served from a separate home GPU machine and communication through Telegram.
- Claude Code writes a specification; Kimi Code implements it in a sandboxed worktree with repository-limited access.
- Hermes runs the test gate and handles Git and GitHub while Copilot CLI reviews the changes and Claude Code gives a final model verdict.
A developer posting as /u/msalsas reports using Hermes Agent on a 4GB Raspberry Pi to coordinate three coding CLIs. The concrete result was llama-doctor, a read-only diagnostic tool for llama.cpp servers. The author reports 378 passing tests, two model reviews and a public repository.
The work was divided by role. Claude Code wrote the specification and gave the final verdict on the diff. Kimi Code implemented the change in a sandboxed worktree. Copilot CLI provided a separate review and could substitute when another service was unavailable. Hermes ran the test gate and handled Git, GitHub and Telegram communication. Its Qwen model ran on a separate home RTX 5080 machine, so the Raspberry Pi was the coordinator, not the machine serving inference.
The author says each coding session used bubblewrap with only the repository bind-mounted and a scoped GitHub token. These are reported access restrictions, not an independently audited security boundary. The source does not establish a human approval gate before merge, and two model reviews should not be described as two human reviewers.
An author comment supplies the missing repository link and explains that llama-doctor reads server metrics, properties and slots to diagnose bottlenecks and pressure. It uses only the standard library and needs no agent at runtime. The AI use case is building and checking that tool. The reported test count and successful build have not been independently reproduced in this editorial review.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Reddit · /u/msalsas
Frequently asked questions
Did the Raspberry Pi run all of the models locally?
No. Hermes ran on the Pi, but the author says its Qwen model was served from a separate RTX 5080 machine. Coding work also used external coding CLIs.
Does the finished diagnostic tool require an agent?
No. In an author comment, msalsas describes llama-doctor as standard-library-only with no agent needed. Agents participated in its development and checks, not its runtime diagnostics.
More details
Remaining steps
- The author shares llama-doctor and clarifies its read-only server endpoints and non-agent runtime.
About this account
Hermes orchestrated coding CLIs, ran the test gate and handled Git and GitHub. Separate model sessions specified, implemented and reviewed the diagnostic tool.
Saved first-person Reddit body and returned comments reviewed on 2026-10-20: https://www.reddit.com/r/hermesagent/comments/1x9ptoo/harness_of_harnesses_hermes_on_a_4gb_rpi_driving/ Results are author-reported, not independently reproduced. No live source or linked artifact was fetched during this editorial review. Suggested prompt is an editorial reconstruction, not the author's original prompt.
Credit: /u/msalsas on r/hermesagent
Source published
Added to Agents In Use
Source checked
Tools and topics
Hermes Agent · Claude Code · Kimi Code · Copilot CLI · Qwen3.8-Flash-Next GGUF · Raspberry Pi OS Lite · bubblewrap · Git · GitHub · Telegram
Multi-agent coding · Raspberry Pi · Diagnostics
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.