15:I[981,["658","static/chunks/658-a698693f56d0116a.js","183","static/chunks/183-6beeeb801c274aaa.js","474","static/chunks/app/%5Btype%5D/layout-631c4730b83c8223.js"],"Posts"] 16:T7b5,Hey HN,

I made Clash, an open-source cli tool that helps you/your coding agent manage merge conflicts that occur during parallel development on the same repository.

Example: Two agents working on different features both modify src/main.rs. Clash shows you this conflict immediately and not after lots of time and tokens spent during the merge time.

It is a simple tool that your agent can use as part of the development process to check if the commits agents make are conflicting with any other worktrees in the repo. This helps pre-emptively capture merge conflicts before feature completion and helps make the merging together of different features into main branch much easier.

Unlike git, which only shows conflicts at merge time, Clash detects conflicts between all active worktrees during development. It's 100% read-only & never modifies your git repo and outputs JSON so agents can adapt their approach before wasting time.

With all of us moving to a world of Managing coding agents rather than being a coding agent themselves, we would be working on multiple different features & bug fixes which unlocks the new ability to have merge conflicts with ourselves.

The vision with clash is to be a tool, that help coordinate internal agents amongst themselves.

  Example workflow:
  - Agent 1 commits changes to src/main.rs in worktree A
  - Agent 2 commits changes to src/main.rs in worktree B
  - Both run `clash status --json` after committing
  - They see the conflict and coordinate to avoid incompatible changes

To better showcase the clash in action, we have added a number of gifs on Clash in action in the github repo.

I’d be interested in feedback on how this tool would fit into your workflow & any general thoughts you have in this area. Try it out and let me know how

We read the JSON Schema spec so you don't have to

Show HN: I built Clash to avoid conflicts when running AI agents in parallel

Show HN: Non-Linear LLM Chats

The First Café for AI Dates

Male students show more tolerance for political enemies than females for allies

Show HN: LLM Skirmish, an RTS game you play with LLMs

Show HN: ADHD Focus Mate – AI mate to help me stop doomscrolling while coding

Kling 3.0 and 3.0 Omni – Everyone a Director?

Arcan-A12: Weaving a Different Web

Show HN: Humetrical – An Improvement on Team Wellness

Show HN: Flowfile – Visual data pipeline editor (WASM and Polars)

A Copernican Revolution for State Machines – Logic as the Center of Gravity

Alpine: All your work, in one place, organized for you

Slashwork: next generation of work tools

Netflix says users can cancel service if HBO Max merger makes it too expensive

Building a privacy-first, EU-hosted AI chat in Rust (Leptos)

Ask HN: On average how many spontaneous erections you have per day?

I used an original iPod Nano in 2026, and it worked surprisingly well

Enforcing rules and managing expectations for AI agents with CI and code review

Why is no-one being prosecuted over the Epstein files? [video]

Software engineer who scaled a startup from 10→500, seeking early-stage roles

How to Succeed and Thrive in a Career You Love [video]

Do things like Oh My OpenCode work?

Nintendo Switch becomes gaming giant's best-selling console in history

Crowd Control vs. Freedom of Association

Taming a flat AST: ergonomics without allocations

Bugs that the Rust compiler catches for you

Linux as daily driver, three months in

Show HN: Next.js-Based SaaS Framework

Context Rot: Why AI Gets Worse the Longer You Chat (and How to Fix It)

Ask HN: Are ISPs "evil" and who runs the Internet?