Foremerge
Foremerge is an open-source coordination protocol that runs above Git to prevent merge conflicts caused by parallel AI coding agents. Instead of detecting conflicts at merge time (when code is already written), agents publish semantic scopes to a shared SQLite store before editing, and Foremerge raises explainable findings when plans collide. It integrates natively with Claude Code, Codex, and Cursor, tracks which model produced each ChangeSet, and exposes coordination state via CLI, MCP tools, and JSON API. Foremerge is built for software development agencies and engineering teams running multi-agent fleets on the same codebase, where silent conflicts (one agent replaces a class while another extends it in a different file) would otherwise go undetected by Git.
Foremerge is an open-source coordination protocol, integrating with Claude Code, Codex, Cursor, and GitHub. InnovaAI scores it 5.4/10 for agency resale.
Agency Audit
Foremerge is an open-source coordination layer that runs above Git to detect intent conflicts between parallel AI coding agents before they create merge conflicts. Agents publish semantic scopes (e.g., 'I will replace PaymentService') to a shared SQLite store, and Foremerge raises explainable findings when plans collide. It integrates with Claude Code, Codex, and Cursor, making it relevant for software development agencies running multi-agent fleets on the same codebase. Resale potential is narrow: this targets engineering teams and dev shops, not horizontal SaaS buyers. Adoption requires technical ops overhead and agent orchestration discipline.
5.4/10
Depends on volume
2d 1-2 days
- Your agency runs 3+ parallel AI coding agents (Claude Code, Codex, Cursor) on the same project and has experienced silent merge failures where agents undid each other's work in different files.
- You bill clients on a per-project or per-sprint basis and can justify coordination infrastructure as a project cost rather than a monthly retainer.
- Your clients are engineering teams or dev shops with Git expertise and existing multi-worktree workflows, not non-technical stakeholders.
- Your clients are non-technical (marketing, e-commerce, content teams) and cannot operate CLI tools or interpret semantic scope conflicts.
- You need white-label branding or a client-facing portal; Foremerge exposes only CLI and JSON API surfaces.
- Your clients run single-agent workflows or sequential (not parallel) AI coding tasks, where intent conflicts do not occur.
Profit Path
Estimate available after setup inputs
$600–$1.5K/project
Monthly Recurring
From 242 published agency rates in USA, 25th to 75th percentile x 20h of assumed delivery time. Rates are self-reported directory profiles, not observed transactions.
Platform Features
Core capabilities of Foremerge
Intent publication before code changes
Agents declare semantic scopes (e.g., 'symbol:PaymentService=replace') before editing, so all agents on the machine see planned changes in a shared SQLite store. Prevents silent conflicts where two agents edit different files but undo each other's logic.
Explainable conflict detection with rule IDs
When two agents claim overlapping scopes, Foremerge returns structured findings with severity, explanation, and coordination suggestions (e.g., 'destructive_vs_additive: one intent replaces PaymentService while another extends it'). Conflicts surface before any code is written.
Semantic scope claiming and leasing
Agents lease scopes so other agents see who is changing what and when. Prevents duplicate work and clarifies ownership across parallel worktrees on a single machine.
ChangeSet lifecycle tracking
Records each ChangeSet from intent through commit, including which agent and which model produced it. Enables audit trails and cost allocation across mixed Claude and Codex fleets.
Verification checks against Git fingerprints
Foremerge runs verification before accepting a ChangeSet to ensure the code matches the declared intent. Catches agent drift or incomplete implementations.
Multi-interface coordination state exposure
Coordination state is queryable via CLI, MCP tools, and a loopback JSON API, so agencies can build custom dashboards or integrate conflict detection into CI/CD pipelines.
What Makes Foremerge Different
Unique advantages vs similar tools in this niche
Semantic scope vocabulary names contended concepts (symbol, api, schema, migration, contract, env) rather than file paths
vs Git's text-based diff, which only flags overlapping lines in the same fileFile paths miss API, schema, configuration, infrastructure, and cross-language collisions, so Foremerge scopes name the thing that is actually contended.
Deterministic, explainable conflict detection with rule IDs and no LLM in the detection path
vs Model-judged conflict resolution that produces different answers for the same inputsIt never asks a model to judge conflicts, so the same inputs always produce the same answer, and findings carry rule IDs like FM-C001.
Advisory leased claims that never lock files or block agents
vs Hard file-locking coordination where one crashed agent stalls the whole fleetClaims are leased and advisory: overlap produces a warning and shared context, never a lock, so you stay in charge.
Cross-model coordination data from mixed Claude + Codex fleets
vs Single-provider agent tooling that cannot see other models' plansA mixed Claude + Codex run produces the cross-model coordination data nobody else is collecting, with each ChangeSet recording agent and model.
Value Equation
Outcome-likelihood-time-effort assessment for Foremerge
Value math requires real pricing
The Value Equation (dream outcome × likelihood ÷ time × effort) feeds directly into ROI math. Foremerge has no published pricing, so we hold this section until real numbers are available.
Contact ForemergePricing
Platform cost for Foremerge
Custom pricing
Foremerge uses custom/enterprise pricing: rates aren't published publicly. Contact their team directly for a quote.
Contact ForemergeReality Check
Foremerge is advisory-only and does not block agents, so conflict detection depends on team discipline to read and act on warnings before code lands. Setup requires CLI familiarity and Git folder integration, which raises onboarding friction for non-technical client teams. Open-source maintenance and vendor stability are unverified.
Low effort: self-service setup with guided onboarding
How This Accelerates White-Label Services
Who It's For
- ✓software-development-agencies-running-parallel-ai-coding-agents
- ✓engineering-teams-using-mixed-claude-codex-fleets
- ✓teams-with-multiple-git-worktrees-on-one-machine
Acceleration Steps
- 1Sign up and connect your account
- 2Configure publish agent intent with semantic scopes before editing code
- 3Connect Claude Code
- 4Launch your first client project
Academy for Foremerge
Work through it in order: the course for this service first, then the modules behind it.
No Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Wiring Over WidgetsConcept
The AI agent itself is a commodity, but the value for agencies lies in the integration layer: connecting a pre-built agent to a client's CRM, calendar, and review cycle. This framework shifts focus from selecting the 'best' agent to mastering the wiring process. For example, an agency using Vendasta's white-label AI receptionist for a local business must configure it to match the client's booking rules and follow-up cadence, turning a generic tool into a tailored service. As agentic AI adoption grows (77% of decision-makers now run agents in production), clients expect this customization. Agencies that treat agents as components and invest in repeatable wiring processes can charge retainers for ongoing optimization, rather than one-off setup fees.
- Wiring Over WidgetsConcept
The AI agent market sells finished workers, but the strategic value for agencies lies not in the agent itself, which is increasingly a commodity, but in the wiring that connects it to a specific client's CRM, calendar, and review cycle. This framework, 'Wiring Over Widgets,' argues that agencies that treat agents as components rather than products win. The agent is the widget; the wiring is the integration, customization, and ongoing optimization that turns a generic tool into a tailored solution. For example, a white-label platform like Vendasta provides AI employees, but the agency's role is to configure them for each local business's unique lead flow and follow-up process. This wiring is where retainer pricing originates, as it requires ongoing maintenance and adjustment. Recent research shows that 88% of B2B marketers face foundational gaps, meaning clients need help not just deploying agents, but ensuring their operations can support them. Agencies that master the wiring can charge a premium for the irreducible value they add.
- Integration MoatConcept
The Integration Moat framework holds that the durability of an AI agent engagement is determined by how deeply the agent is wired into a client's existing systems, not by the agent's underlying capability. Since the agent itself is increasingly a commodity, the switching cost for the client lives in the integrations: the CRM fields mapped, the calendar sync, the review-cycle triggers, and the exception-handling rules. Agencies that invest in this wiring create a moat that competitors offering generic agents cannot cross. For example, a white-label platform like Vendasta lets an agency deploy an AI receptionist for a local business, but the real value is in configuring it to the client's booking flow and follow-up cadence. With 77% of AI decision-makers now running agentic AI in production, clients expect this depth, and agencies that deliver it convert one-off projects into retainers.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- AI Agents Rule: Wire the Agent, Not the ProductEvaluation Rule
Treat the AI agent as a commodity component and focus your value on the integration into the client's specific workflows, systems, and review processes.
- AI Agents Rule: Wire the Agent, Not the ProductEvaluation Rule
Treat the AI agent as a commodity component and charge for the integration into the client's specific systems and workflows.
- The Productized Agent Trap: Why AI Agent Services Stall Without Client-Specific WiringFailure Pattern
- The Agent-as-Product Trap: Why AI Agent Services Stall Without Client-Specific WiringFailure Pattern
8 modules selected for Foremerge
Frequently Asked Questions
Answers about pricing, setup, implementation
Foremerge is an open-source coordination protocol that sits above Git and detects intent conflicts between parallel AI coding agents before they become merge conflicts. Agents publish semantic scopes to a shared SQLite store before editing code, and Foremerge raises explainable findings when plans collide. It tracks which agent and model produced each ChangeSet and exposes coordination state via CLI, MCP tools, and JSON API.
Foremerge is open-source and free to use. No pricing tiers or commercial plans are published.
No verified white-label program exists. Foremerge exposes coordination state via CLI and JSON API only, with no client-facing dashboard or branded portal. Resale would require building your own interface layer on top of the API.
Yes. Foremerge is built to work natively with Claude Code, Codex, and Cursor. Agents install Foremerge via a one-line setup command and then publish intent and read conflict findings through the shared SQLite store and CLI.
Initial setup is a one-line install command that wires Foremerge into the project's .git folder. Per-agent onboarding (Claude Code, Codex, Cursor) requires pasting the MCP setup configuration, which takes under 5 minutes per agent. Ongoing coordination is automatic once agents are configured.
Foremerge is built for software development agencies, engineering teams using mixed Claude and Codex fleets, and teams with multiple Git worktrees on one machine. It is not a fit for non-technical verticals (e-commerce, marketing, content) or single-agent workflows.