naw103
Foremerge is an open-source coordination protocol for parallel coding agents, built above Git. It lets agents publish intent, semantic scopes, dependencies, provisional ChangeSets, decisions, validation, and provenance in a shared local store so conflicts are identified before they become merge problems.
At a Glance
- Teams and individuals using multiple autonomous coding agents
- Software engineering organizations using Git worktrees and parallel branches
- Developer-tool, DevOps, and agent-infrastructure teams
- MCP-capable coding-agent users and tool builders
AI Tools by naw103
(1)
Foremerge
AI Agent Coordination Protocol
Discussions
No discussions yet
Be the first to start a discussion about naw103
Latest News
Foremerge v0.5.0 released with trusted named-check validation for the HTTP API
Foremerge v0.4.3 released with version-aware ledger upgrade and recovery improvements
Blog: AI agents introduced several new layers to the development stack; Foremerge argues coordination is the missing layer
Blog: Agent orchestrators and agent coordinators are not the same layer
Products & Services
Apache-2.0 open-source, local-first coordination layer above Git. Agents publish intents, claim semantic scopes, detect deterministic conflicts, publish ChangeSets, run trusted verification, and record acceptance/provenance in a shared SQLite store.
A single installable binary for initializing repositories, registering agents, publishing intents, claiming work, checking conflicts, managing ChangeSets, configuring checks, and inspecting status. Distributed through checksum-verified binaries, crates.io, and source installation.
An stdio MCP interface exposing 18 coordination tools, including publish_intent, claim_work, check_conflicts, publish_changeset, run_verification, and accept_changeset.
Authenticated loopback HTTP API with an OpenAPI schema for harnesses that prefer HTTP to stdio.
Market Position
Foremerge positions itself as a coordination layer above Git rather than a replacement for Git, code review, CI, worktrees, or orchestration. Its differentiators are declared semantic intent instead of only file diffs, deterministic and explainable rules instead of a judge model, advisory claims instead of deadlocking locks, and verification/provenance before acceptance. It is complementary to agent orchestrators and file/worktree locking tools; its stated limitation is that detection remains heuristic, local-first, and pre-1.0.
Leadership
Founders
Nick Woodhead
Technology executive, CTO, full-stack engineer, and founder with 20+ years guiding engineering teams through large-scale e-commerce, ERP, fintech, and CPG projects. His GitHub profile identifies him as the creator of Foremerge and links him with Corgen LLC, GPTree, and TranslateTech-related work.
Executive Team
Nick Woodhead
Founder and maintainer
Technology executive, CTO, full-stack engineer, and GitHub maintainer; his public profile describes 20+ years of experience across e-commerce, ERP, fintech, and CPG engineering programs.
Founding Story
Woodhead built Foremerge after experiencing a silent failure while running Claude Code, Codex, and Cursor in parallel Git worktrees for GPTree: one agent replaced PaymentService while another added PayPal support to it. The worktrees and diffs were clean, but the plans were architecturally incompatible. Foremerge was built to make agents declare intent and semantic scopes before editing, and was open-sourced in August 2026.
Business Model
Revenue Model
The core product is free and open source under Apache-2.0. The project says GitHub Sponsors supports maintenance; its roadmap contemplates optional team/shared coordination infrastructure as a possible future business, while keeping the local tool free and server-independent.
Target Markets
- Teams and individuals using multiple autonomous coding agents
- Software engineering organizations using Git worktrees and parallel branches
- Developer-tool, DevOps, and agent-infrastructure teams
- MCP-capable coding-agent users and tool builders
- Coordinating Claude Code, Codex, Cursor, and other coding agents working in parallel
- Catching destructive-versus-additive architectural conflicts before implementation
- Preventing duplicate work and contract drift across separate Git worktrees
- Coordinating changes to APIs, schemas, migrations, configuration, and infrastructure that file-level Git comparison misses
- Maintaining verification and provenance records for agent-generated ChangeSets
- GPTree