DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to set up Foremerge for a repo's coding agents with Foremerge

Install Foremerge, initialize the repo, and wire up every agent client you use in one pass.

Remote script. The install step pipes a script from Foremerge.com directly into sh, so review it first if your policy requires that.

Who it is forA team lead who wants Claude Code, Codex, or Cursor to coordinate on a repository and needs a one-time setup that works for each agent.

The problemEach agent client needs its own skill and MCP entry, and setting them up by hand is easy to get wrong.

The outcomeThe repository has local coordination state, every installed client has the Foremerge skill and MCP entry, and doctor reports the setup as working.

What you need first

  • Git and jq installed
  • macOS or Linux, or the Windows binaries from the releases page
  • A Git repository to coordinate, with at least one coding agent or a shell to act as one
  • Rust 1.85+ only if you build from source

Steps

  1. Install with curl -fsSL https://foremerge.com/install.sh | sh.
  2. Run foremerge init inside the repository.
  3. Run foremerge setup all to wire every client you use.
  4. Register the repository's real test command with foremerge checks set test -- cargo test --all-targets, replacing it with your own.
  5. Run foremerge doctor --client all and confirm each client reports OK.

Prompt for your agent

In the <repo path> repository, install Foremerge, run `foremerge init`, then run `foremerge setup all` and `foremerge doctor --client all`. Expected output: a per-client result from setup and a doctor report. Verify that setup exited with status zero, since the README says it exits nonzero if any client failed.

Caveat. Setup asks the client to enable an MCP server and will prompt you before doing so, and the Codex registration is user level and serves every repository.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page