Thread

1. gavmor · 1790132647 · focus · HN ↗

   I've been using a combination of `weave` and ad hoc "blackboard pattern" skills—some self-made, some borrowed—but I haven't really felt they've earned their keep. Maybe I'm not working in parallel enough, or else maybe I'm relying too much on a parent coordinator session to resolve conflicts.

   1. naw103 · 1790184165 · focus · HN ↗

      I encountered similar issues before I built Foremerge, ie auto router, orchestrater and shared blackboard type memory structure. The agents were aware of what was put into memory but still did their own thing and created conflicts. I still see it in claude code today when it creates subagents without Foremerge setup for the project. It resolves itself but you can see it burning through token usage to do so. If your using a single agent you dont necessarily need Foremerge but it still helps when subagents get created automatically and gives you the audit trail of intent decisions essentially at almost zero cost of having the tool installed. Where Foremerge really shines is if you bounce back and forth between claude and codex with no single parent. I dont know Weave well enough to know where it sits. The question I'd ask about any of them is what happens if you kill it? If the agents stop then it's an orchastrator, if the agents continue and you just loosed the shared picture then its a coordinator like Foremerge.

      How many sessions do you typically run at once and are they all children of the same parent?

      1. gavmor · 1790186485 · focus · HN ↗

         Up to ~25, and they're not exactly "children", but I do have a coordinator agent that can selectively intrude on their sessions. I use `aoe` to spawn and communicate between worktree-isolated sessions:

         <a href="https:&#x2F;&#x2F;www.pasteboard.co&#x2F;XirzoTywU6lz.png" rel="nofollow">https:&#x2F;&#x2F;www.pasteboard.co&#x2F;XirzoTywU6lz.png

         1. naw103 · 1790219938 · focus · HN ↗

            I think Foremerge would be extremely useful in your setup especially with 25 agents running in parallel. While aoe manages the physical layout and terminal communication (ie. spawning sessions, executing commands, wrappting tmux etc.), Foremerge would act as your logical synchronization layer that prevents the agents from stepping on each others toes. They should complement each other really well. do you know what causes the coordinator agent to intrude right now? is it both plans being on the blackboard or is it being triggered by diffs or failing merges?

Unofficial Hacker News client; not affiliated with Y Combinator.