Foremerge
Catch intent conflicts before code conflicts: the open-source coordination protocol for coding agents, built above Git.
- What
- Catch intent conflicts before code conflicts: the open-source coordination protocol for coding agents, built above Git.
- Cost
- Free
- Needs
- Coordinate your parallel coding agents with Foremerge.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Foremerge is the open-source coordination protocol for coding agents, built above Git. Run Claude Code in one worktree, Codex in another, or any other agents from any provider: each agent declares what it is about to change (intents, semantic scopes like symbol:PaymentService=replace, dependencies, provisional ChangeSets, decisions) through one shared SQLite store under your repository's Git common directory. When two plans collide, deterministic rules raise an explainable finding while the work is still a plan, with the rule that fired and a suggested resolution. Git still stores the commits; Foremerge stores the shared plan. It is a coordinator, not an orchestrator: claims are leased and advisory, never locks, and nothing ever blocks an agent. The full lifecycle is exposed over a local CLI, a JSON API and an MCP server (17 tools), with one-command client wiring (foremerge setup all handles Claude Code, Codex and Cursor). Acceptance is verification-gated: Foremerge runs your trusted check itself rather than taking an agent's word for it. Honest caveats: this is a pre-1.0 local-first MVP (0.5.1), so public schemas may still change. Published benchmark results do not exist yet, and coordination between machines is out of scope. Conflict detection is heuristic and advisory: it warns, it never locks.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Coordinate your parallel coding agents with Foremerge. Easiest way: paste this into your coding agent (Claude Code, Codex or Cursor) from inside the repository you want to coordinate: Set up Foremerge in this repository so we can coordinate parallel agents. 1. Install it: curl -fsSL https://foremerge.com/install.sh | sh 2. Initialize: foremerge init 3. Wire this client and any others in use: foremerge setup all 4. Register the check I should be validated against, for example: foremerge checks set test -- <your test command> 5. Confirm: foremerge doctor --client all Or do it yourself (you need a recent Git; jq is handy for the JSON examples): 1. Install the prebuilt, checksum-verified binary (macOS and Linux, installs to ~/.local/bin): curl -fsSL https://foremerge.com/install.sh | sh. Alternatives: npm install -g foremerge (macOS, Linux with glibc, Windows x64), or from source with Rust 1.85+: cargo install --locked --git https://github.com/naw103/foremerge foremerge. 2. Inside your repository: foremerge init (creates local coordination state under the Git common directory, touches no tracked files). 3. Wire your clients: foremerge setup all (or setup codex, setup claude, setup cursor individually). 4. Register the trusted check agents will be validated against: foremerge checks set test -- <your test command>, then confirm with foremerge doctor --client all. 5. Done: each agent now publishes its intent with semantic scopes before editing, and checks for conflicts before starting. Official docs: https://foremerge.com, repo: https://github.com/naw103/foremerge (Apache-2.0)
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.