‹ BackHN Continuity

Thread

Show HN: Foremerge – Catch intent conflicts between parallel coding agents

45 points · 20 comments · naw103

  1. adityamishra241 · · focus · HN ↗
    This is interesting. How do you decide whether a detected conflict is actually worth stopping the agent for? I imagine some overlapping changes could still be perfectly fine.
    1. naw103 · · focus · HN ↗
      It dosnt stop an agent, claims are advisory. I mostly answered this in my comment of questions that I normally get asked above. The only hard stop is at acceptance, and only for HIGH signals. HIGH is reserved for something the toll can state as fact rather than guess about. ie. both agents declared the same scope and one agent destroys (replace, rename, remove) the thing the other agent is building on (extend, modify). Whether an overlap is fine is a judgement that Foremerge dosnt make itself and thats by design. The agents are smart enough and determine this themselves after receiving the advisory. For a HIGH signal the agents coordinate through messages and either agent resolves it with a logged rationale that unblocks it for both (a human can override it with a logged reason too). The idea is that every path out leaves a decision log behind so later you can see not just that two plans overlapped but what was decided and why. (I think this has a good compliance angle to it as well)
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.