Catch conflicting plans between parallel coding agents before they merge

A team running several coding agents on one repo built a tool to catch intent conflicts Git cannot see.

Difficulty
IntermediateOur rating
Time to build
Not reportedOur estimate
Monthly cost
Not reported
Revenue
Not reportedWe only show revenue the source states
Engagement
45 HN points20 comments · fetched Oct 15, 2026

What they did

naw103’s team at GPTree runs parallel agents in worktrees. The worst failures were plans that could not both be true, like one agent replacing a class another was extending, so they built Foremerge.

How it went

Open-sourced on GitHub.

Worth knowing

Git only notices textual conflicts, not architectural ones.

Builder recipe

Our own starting point, written from the source. Adapt it to your setup.

Stack

  • Foremerge
  • Parallel worktrees

Steps

  1. Open the repo in your coding agent and describe the goal and constraints.
  2. Ask for a plan first, then let it implement in small, reviewable steps.
  3. Run the tests or the app after each step and feed errors back.
  4. Review the diff before merging.

Starter prompt

Compare the plans in /plans/*.md. List any two plans whose changes cannot both be true and suggest an order or merge.

Open the repo ↗ (opens in new tab)

Tags

Read the original

Related use cases

no count
NEW Coding

Design mobile apps by chatting with AI

Sleek turns a chat about an app idea into polished mobile app designs in minutes.

💰 $20,587 MRR, verified via Stripe on TrustMRR (synced 2026-10-15)Advancedby Stefano
no count
NEW Coding

Turn screenshots into working front-end code

Screenshot to Code converts a screenshot, mockup, recording or prompt into HTML/Tailwind, React or Vue, then refines it from plain-English follow-ups.

💰 $4,768 MRR, verified via Stripe on TrustMRR (synced 2026-10-15)Advancedby Abi Raja

The Daily 5.

Five real AI agent use cases each morning, each with a recipe and a source. Plus a Sunday roundup. Free.