Practical overview
When it fits
Use Foremerge when coding agents work in parallel on the same repository and Git’s text-based merge checks may not reveal conflicting intent.
Who it is for
- Developers coordinating multiple coding agents on the same repository.
- Teams using isolated Git worktrees that need agents to see one another’s planned changes.
Documented uses
- Publish an agent’s intended targets and semantic scopes before editing.
- Surface potentially conflicting plans even when agents are changing different files.
- Track dependencies and provisional changesets across agent contributions.
- Record decisions, validation outcomes and provenance for coordinated work.
Requirements & limits
The project documents CLI installation through an install script, npm on macOS or Linux with glibc, and Cargo. Manual setup requires recent Git and jq; building from source requires Rust 1.85 or later.
- Foremerge warns about declared intent conflicts but does not lock files or block agents; people remain responsible for deciding how to resolve them.
- Its shared coordination store is local to the repository, and coordinating between machines is outside project scope.
- It is a pre-1.0 MVP, and public schemas may change.
- The README names Claude Code, Codex and Cursor and documents connecting clients through setup that enables an MCP server.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and initialize Foremerge in a repository
Install the CLI, initialize Foremerge, and connect coding-agent clients for repository coordination.
Before you start
- Recent Git and jq for the documented manual setup.
- A repository to coordinate.
- A supported installation route: the install script, npm on macOS or Linux with glibc, or Rust 1.85+ for building from source.
Steps
Install Foremerge using the project’s install script, npm package, or documented Cargo command.
From the repository, run
foremerge init.Connect the clients in use with
foremerge setup all; approve the prompt to enable the MCP server when requested.Run
foremerge doctor --client allto confirm the client setup.
Expected outcome
Foremerge is initialized in the repository and the selected clients are wired to its coordination setup.
Guide limitations
- The npm package is documented for macOS or Linux with glibc; the Windows npm package is not published.
- Foremerge is a pre-1.0, local-first MVP. Coordination between machines is outside its scope, and public schemas may change.
- This is setup guidance; it does not verify that a particular coding-agent workflow or validation command succeeds.
Compare options for Agent orchestration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Foremerge | Publish an agent’s intended targets and semantic scopes before editing. | CLI | The project documents CLI installation through an install script, npm on macOS or Linux with glibc, and Cargo. Manual setup requires recent Git and jq; building from source requires Rust 1.85 or later. |
| Agenite | Define typed tools with JSON Schema validation and error handling. | CLI | |
| Veldra | Create an agent with a policy, tools, skills, knowledge base and reasoning method. | Self-hosted | The documented deployment is self-hosted and uses a sign-in gate after a first-run administrator account is created. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- naw103/foremerge · Official homepage title · retained in its source language