foremerge.com

mx

route2.mx.cloudflare.net

route1.mx.cloudflare.net

route3.mx.cloudflare.net

ns

norm.ns.cloudflare.com

ruth.ns.cloudflare.com

caa

txt

google-site-verification=YvQYv4DV1aXCy7G07LpgRgUZiIyj3L11cn4m3mpFJtY

v=spf1 include:_spf.mx.cloudflare.net ~all

prod-verif-shipyard-11a4ac9cd9d0

dmarc

v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;

User-agent: *
Allow: /
Sitemap: https://foremerge.com/sitemap.xml

# Foremerge
> Coordination protocol for coding agents, built above Git. Agents publish
> intent and claim semantic scopes with declared operations before writing
> code; deterministic rules raise findings when plans collide. One Rust
> binary, local-first, Apache-2.0.
## Docs
- [README](https://github.com/naw103/foremerge#readme)
- [MCP setup](https://github.com/naw103/foremerge/blob/main/docs/mcp-setup.md)
- [Conflict detection](https://github.com/naw103/foremerge/blob/main/docs/conflict-detection.md)
- [Limitations](https://github.com/naw103/foremerge/blob/main/docs/limitations.md)
## Writing
- [Parallel coding agents without the carnage](https://foremerge.com/blog/parallel-coding-agents-without-the-carnage/)
- [The coordination layer you are probably missing](https://foremerge.com/blog/the-coordination-layer/)
- [31 hard questions about coordinating parallel coding agents](https://foremerge.com/blog/31-questions-coordinating-parallel-coding-agents/)
- [Orchestrators and coordinators are not the same layer](https://foremerge.com/blog/orchestrator-vs-coordinator/)
- [Running multiple Claude Code agents in parallel](https://foremerge.com/blog/running-multiple-claude-code-agents-in-parallel/)
## Install
- macOS and Linux: `curl -fsSL https://foremerge.com/install.sh | sh`
- npm on macOS and Linux: `npm install -g foremerge`
- With Rust: `cargo install --locked foremerge`
- Windows: binaries on the [releases page](https://github.com/naw103/foremerge/releases)