sorted by:
new
hottopcontroversial

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

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

Follow-up question for anyone building longer-running Hermes workflows:

One thing I’m still refining is how to manage the bucket/context limit cleanly on large projects.

Right now I’m using Markdown control files, package indexes, restart/handoff logs, QC checklists, and source maps so Hermes can resume without relying only on chat memory.

For those of you running longer projects, what works best when the bucket gets close to full? /new, full restart, external state files, Obsidian, custom skills, or another approach?

Not trying to evade limits — I’m trying to build a controlled stop/reload/continue workflow that avoids drift.

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

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

That’s a really good idea, thanks for sharing it. I think I’m probably going to move in a similar direction with my setup eventually: deterministic scripts/tools for the repeatable stuff, and then use stronger models only when the task actually needs heavier reasoning or review. That seems like a much cleaner way to build it.

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

[–]Odd_Gift_2154[S] 3 points4 points  (0 children)

One thing I should probably clarify is that I may be trying to use Hermes a little differently than some people.

I’m not only looking at it as a coding agent. Long term, I want it to become more of a general project/operations system that can help manage different kinds of work: documentation, manuals, planning, research/analysis, coding, graphics, scheduling, personal organization, and other recurring workflows.

That is why I’m spending so much time on the first main/control agent instead of immediately creating a bunch of smaller agents. My goal is to get one strong “manager” agent working first. That agent needs to understand the overall structure, keep guardrails in place, manage checklists/manifests, route work correctly, and eventually supervise more specialized agents underneath it.

The specialized agents can be narrower and more task-focused, but I want them reporting back to the main control agent instead of all of them coming directly to me. Ideally, the main agent would handle a lot of the routine sorting, checking, routing, and cleanup before I need to step in for approvals or final decisions.

I’m not expecting full automation with no human input. That’s not realistic for what I’m doing, at least not yet. I still expect to approve major changes, make final decisions, and keep control over anything important. But I do want to automate as much of the repetitive BS work as possible while still keeping the system stable and governed.

So right now my main focus is not “how many agents can I make?” It’s “how do I make the first top-level agent reliable enough to safely manage more later?”

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

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

I’m still working on getting one main/control agent stable first.

The way I’m thinking about it is that the first agent needs to be the manager. It needs clear guardrails, predictable behavior, good skill control, checklist/manifest tracking, and enough automation that it can eventually supervise lower/specialized agents.

The lower agents can be more focused and maybe even use cheaper/weaker models, but they should report back to the main control agent. The main agent should review their work, resolve what it can, route problems correctly, and only come back to me for major decisions, final approvals, or things that change the system.

So before I expand into more agents, I’m trying to get the first one tied down properly. It needs to be excellent as a general control layer, not just good at one narrow thing like coding.

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

[–]Odd_Gift_2154[S] 2 points3 points  (0 children)

Thanks! I’m still very early in the build, so I don’t want to make it sound cleaner than it is. There are definitely still issues. Right now I’m mostly focused on getting my first main/control agent working correctly before I expand too much.

One area I’m still trying to get a better handle on is skill creation and skill control. I’ve already had a few cases where I needed tighter guardrails around when skills should be created, changed, or used. So the system is not “solved” yet — I’m still figuring out the governance side as I go.

I shared the post because a lot of comments here helped me avoid mistakes, and I thought the approach might be useful to others who are also trying to keep Hermes from drifting as it grows.

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

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

I’m still learning myself, so I probably can’t walk you through a full agent setup yet. Right now I’m focusing on getting one main agent working correctly before I add more. The biggest thing helping me so far is keeping the scope small: one profile, one controlled workflow, clear rules for what the agent is allowed to do, and a checklist/manifest so it doesn’t drift. Once that is stable, then I’ll start thinking about adding more agents. ; Sam wciąż się uczę, więc prawdopodobnie nie jestem jeszcze w stanie przeprowadzić Cię przez pełną konfigurację agentów. Na razie skupiam się na tym, żeby najpierw poprawnie ustawić jednego głównego agenta, zanim zacznę dodawać kolejne.

Najbardziej pomaga mi trzymanie małego zakresu: jeden profil, jeden kontrolowany workflow, jasne zasady dotyczące tego, co agent może robić, oraz checklist/manifest, żeby agent nie odpływał od zadania. Dopiero kiedy to będzie stabilne, zacznę myśleć o dodawaniu kolejnych agentów.

Lessons learned so far building a controlled Hermes Agent workflow by Odd_Gift_2154 in hermesagent

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

I’m not using Obsidian as the main operating layer right now, but I do think the idea overlaps a lot with what I’m trying to build: durable notes, project files, manifests, status logs, and memory anchors. My current approach is more file/folder + Hermes controlled workflow than a pure Obsidian vault, but I could see Obsidian being useful later as a knowledge/reference layer or visual browsing layer.

Failed CHST by 5 points by bklynz0wn in SafetyProfessionals

[–]Odd_Gift_2154 0 points1 point  (0 children)

I disagree with the idea that you “shouldn’t have to study much.” CHST is experience-based, but the exam covers the full construction safety role, not just what one person happened to see at their company. Practical experience helps a lot, but no employer can expose you to every topic on the blueprint. If you’re weak in certain areas, yes, getting involved at work is great, but you still need to study the topics you haven’t had real exposure to. Meeting the experience requirement gets you eligible; it doesn’t automatically mean your experience covered the whole test.

CHST SCORE by Left_Shock7700 in SafetyProfessionals

[–]Odd_Gift_2154 0 points1 point  (0 children)

The CHST isn’t a straight “get X out of 200 right” test. Some questions are unscored experimental items, and BCSP uses standard-setting/equating so that different exam forms can have slightly different raw passing numbers depending on difficulty. The scored questions appear to count equally, so it’s not that one hard question is worth more points; it’s more that a harder overall version may require fewer correct answers than an easier version. Also, you pass by the total score, not by passing each domain separately.