foremerge

Changes to the facts recorded here, not a live scan of every vendor update. Save this tool to follow updates in your account.

1. 11/1/2026

   Updated: features, limitations, platforms, summary, use cases, walkthrough

   See recorded changes

   features

   Before: ["Agents publish their intended changes before editing, specifying the target scope such as a function name. This intent sharing allows detection of conflicting plans before code is changed.","Foremerge maintains a small database inside the project's .git folder that all agents read from and write to, providing a shared picture of planned changes.","Foremerge detects and explains conflicts between agents' plans, naming the agents involved, describing why their plans clash, and suggesting how to split the work, all before any code is changed."]

   After: ["Agents declare their intended changes before implementation to avoid conflicts.","Foremerge maintains a small database inside the project's .git folder to share intent among agents.","Foremerge detects and explains conflicts between agents' plans before any code is changed, providing advisory warnings without locking files or blocking agents."]

   limitations

   Before: ["Foremerge does not lock files or block agents to avoid stalling the whole fleet if an agent crashes, so warnings are advisory and users remain in control. It also does not use a model to judge conflicts, ensuring consistent conflict detection results."]

   After: ["Foremerge does not lock files or block agents to avoid stalling the workflow if an agent crashes; warnings are advisory only.","Foremerge does not use large language models to judge conflicts, ensuring consistent conflict detection results."]

   platforms

   Before: ["Foremerge provides checksum-verified binaries for macOS and Linux, Windows binaries are available on the releases page, and it can be installed via Rust's cargo package manager."]

   After: ["Foremerge provides checksum-verified binaries for macOS and Linux, npm packages for macOS, Linux, and Windows x64, and Rust crates for installation."]

   summary

   Before: "Foremerge is an open-source coordination protocol for coding agents that operates above Git. It enables agents to keep isolated worktrees while sharing intent, semantic claims, ChangeSets, and verification to avoid conflicting changes that Git cannot detect."

   After: "Foremerge is an open-source coordination protocol for coding agents that operates above Git. It enables agents to keep isolated worktrees while sharing intent, semantic claims, ChangeSets, and verification to avoid conflicts that Git cannot detect by comparing text alone."

   useCases

   Before: ["Coordinating multiple AI coding agents working on the same project simultaneously to avoid conflicting changes that Git cannot detect. This is especially useful when agents edit different files but with overlapping intent."]

   After: ["Coordinating multiple AI coding agents working simultaneously on the same project to prevent conflicting changes.","Detecting semantic conflicts in code changes that Git cannot detect because it compares text rather than intent."]

   walkthrough

   Before: ["Install Foremerge by running a shell script from the official site or via Rust's cargo. Initialize the repository with 'foremerge init' and set up clients with 'foremerge setup all'. Register a test command for validation and confirm setup with 'foremerge doctor --client all'.","After setup, agents publish their intent with semantic scopes before editing, claim the scope, and check for conflicts before starting work."]

   After: ["Install Foremerge using the provided script or package managers, initialize it in the repository, set up clients, register validation checks, and confirm setup.","Publish your intent with semantic scopes before editing, claim the scope, and check for conflicts before starting work."]

2. 9/14/2026

   Updated: features, limitations, platforms, summary, use cases, walkthrough

   See recorded changes

   features

   Before: ["Agents declare their intended changes before implementation to avoid conflicts.","Foremerge maintains a small database inside the project's .git folder to share coordination state among agents.","Foremerge provides advisory warnings about conflicting plans without locking files or blocking agents."]

   After: ["Agents publish their intended changes before editing, specifying the target scope such as a function name. This intent sharing allows detection of conflicting plans before code is changed.","Foremerge maintains a small database inside the project's .git folder that all agents read from and write to, providing a shared picture of planned changes.","Foremerge detects and explains conflicts between agents' plans, naming the agents involved, describing why their plans clash, and suggesting how to split the work, all before any code is changed."]

   limitations

   Before: ["Foremerge does not lock files or block agents, so warnings are advisory and conflicts must be resolved by users.","Foremerge does not use language models to judge conflicts, ensuring consistent conflict detection results."]

   After: ["Foremerge does not lock files or block agents to avoid stalling the whole fleet if an agent crashes, so warnings are advisory and users remain in control. It also does not use a model to judge conflicts, ensuring consistent conflict detection results."]

   platforms

   Before: ["Foremerge provides checksum-verified binaries for macOS and Linux, and Windows binaries are available on the releases page; it can also be installed via Rust's cargo."]

   After: ["Foremerge provides checksum-verified binaries for macOS and Linux, Windows binaries are available on the releases page, and it can be installed via Rust's cargo package manager."]

   summary

   Before: "Foremerge is an open-source coordination protocol for coding agents that operates above Git. It enables agents to keep isolated worktrees while sharing intent, semantic claims, ChangeSets, and verification to prevent conflicting changes that Git cannot detect."

   After: "Foremerge is an open-source coordination protocol for coding agents that operates above Git. It enables agents to keep isolated worktrees while sharing intent, semantic claims, ChangeSets, and verification to avoid conflicting changes that Git cannot detect."

   useCases

   Before: ["Coordinating multiple AI coding agents working on the same project to avoid conflicting changes."]

   After: ["Coordinating multiple AI coding agents working on the same project simultaneously to avoid conflicting changes that Git cannot detect. This is especially useful when agents edit different files but with overlapping intent."]

   walkthrough

   Before: ["Install Foremerge via a shell script or cargo, initialize it in the repository, set up clients, register test commands, and confirm setup.","Agents publish their intent with semantic scopes before editing, claim the scope, and check for conflicts before starting work."]

   After: ["Install Foremerge by running a shell script from the official site or via Rust's cargo. Initialize the repository with 'foremerge init' and set up clients with 'foremerge setup all'. Register a test command for validation and confirm setup with 'foremerge doctor --client all'.","After setup, agents publish their intent with semantic scopes before editing, claim the scope, and check for conflicts before starting work."]