It looks very promising! Is there any plan to implement a ralph-loop inside?
Show HN: Agent-harness-kit scaffolding for multi-agent workflows
11–20 of 33 posts
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#12hit this exact thing running a routines hub.
When an agent is told to do something by the scheduler, the next step in the process only believes it’s done if the agent’s status is marked as ‘posted’. Statuses like ‘ready_to_post’ or ‘draft_verified_awaiting_review’… these are actually errors that the system needs to fix on the following attempt.
The trickiest part was dealing with being stopped, but not having something break. You have to have ways to say “this happened, and it isn't what we wanted”, for example, ‘blocked_quota’, ‘blocked_no_credentials’, or ‘skipped_anti_bunching’. If you don't have those, the main program will endlessly retry and spend all your money.
the typed handoff in ahk is the right primitive imo. discipline on top: agents never write half-states. every run terminates in a documented terminal status, success or otherwise.
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#13This looks really cool. Did you think about including automatic worktree creation + sandboxing?
I've built sth similar (more focus on the project setup and being able to work on multiple things at once with a single agent), that uses git worktrees to create a separate space (symlinks .env files) and bubblewrap to isolate the worktree for the agent.
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#14This is very cool.
We have been working on a communication layer that would be, I believe, complementing it by allowing the agents to actually talk to each other and to agents in other teams: https://github.com/awebai/aweb
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#15looks interesting, starred
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#16This is very cool. We have been working on a communication layer that would be, I believe, complementing it by allowing the agents to actually talk to each other and to agents in other teams: https://github.com/awebai/aweb
I vibe coded a super simple communication layer with my agents. I'm all for it as certain things shouldn't be put in certain contexts for one.
I have a lot more roles though and it's more flexible, but also a bit slower as it isn't in full yolo mode.
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#17This is very cool. We have been working on a communication layer that would be, I believe, complementing it by allowing the agents to actually talk to each other and to agents in other teams: https://github.com/awebai/aweb
I vibe coded a super simple communication layer with my agents. I'm all for it as certain things shouldn't be put in certain contexts for one. I have a lot more roles though and it's more flexible, but also a bit slower as it isn't in full yolo mode.
How are you finding the communication between your agents? Ours is really interesting - they are developing personalities. Sometimes being quite passive aggressive with each other
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#18doesn't codex already offer subagents i can see this is agnostic but unsure i would add to the context load on each turn
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#19Two questions on the design: "lead-agent reads sub-agent output" makes the lead an LLM judge. Are there post-conditions checked, or is LLM-judge approval the final gate? Related: does the system reason over typed state or over raw output?
Re: Show HN: Agent-harness-kit scaffolding for multi-agent workflows
#20Earlier quoted context omitted.
I vibe coded a super simple communication layer with my agents. I'm all for it as certain things shouldn't be put in certain contexts for one. I have a lot more roles though and it's more flexible, but also a bit slower as it isn't in full yolo mode.
How are you finding the communication between your agents? Ours is really interesting - they are developing personalities. Sometimes being quite passive aggressive with each other
Hmm... they remain similar-ish. But I think that's also because I have a lot in my claude.md file that they have to follow empiricism as a philosophy. Things need to be verified, researched, backed by data, etc.
That's also how I live my life, so when it starts to develop a personality, usually I'd ask what the benefit of that is. If it doesn't have a good answer, then I have yet another rule in my CLAUDE.md about what it should or should not do.
The communication, more or less, goes as I want it to go, aka quite smooth.