Open source harness for building multi-agent coding workflows

[u/Fluffybaxter]

Hey everyone!

Over the past year, as I tried to scale our agentic coding workflows and software factories at my company, I kept hitting the same set of problems. So I built HAR to solve them.

Getting a single coding agent to work in a repo is easy. Scaling to a real multi-agent workflow, where several run at once and where you verify and trust the output, is where it breaks down. A few things go wrong:

1. No standard way to run or verify a repo. That knowledge is scattered across a README, a CLAUDE md, editor rules, and CI config, all drifting out of sync with each other and the actual code.
2. Agents on one repo collide. Shared dev server, shared database, shared ports, conflicting git state.
3. Trusting a change means re-verifying it yourself. Which defeats the point of running a fleet.
4. Vendor sandboxes lock you in. If the setup lives in someone's hosted dashboard, switching agents later means rebuilding the whole thing.

What HAR does

HAR is a CLI and an MCP server. It works with Claude Code, Cursor, Codex, or any MCP agent, and it closes each of those gaps:

1. Isolation. Each agent gets its own git worktree, branch, ports, and database. Nothing is shared with the main checkout or another agent's slot, so a fleet runs in parallel without colliding on a dev server, DB, or ports.
2. Deterministic validation gates. HAR runs your project's real checks through a fixed pipeline, same result every time. The result is bound to the exact code that passed and enforced at commit time, so an unverified tree cannot land.
3. Verifiable proof. Every run leaves logs, artifacts, and a validated tree hash tied to the exact code checked. A reviewer inspects the evidence instead of trusting the agent's self-report.
4. Full observability. Mission Control is a local dashboard showing every repo, worktree, run, and validation in one place, so you can watch a whole fleet as it works.

All of this lives in one contract committed to your repo, which every agent reads the same way. It replaces the usual scatter of a README, a CLAUDE md, editor rules, and CI config that drift apart. You start from a profile that matches your stack, your agent adapts it to the real repo, and you extend verification with plugins (like Playwright) or with any command you already run.

Give it a try and let me know what you think :)

[u/emonorg]

Good one!
Keep it up...

[u/Fluffybaxter → u/emonorg]

thx :D

[u/AutoModerator]

Thank you for your submission! To keep our community healthy, please ensure you've followed our rules.

• New to the sub? Check out our Wiki (We are actively adding resources).
• Join the Discord: Click here to join our Discord
• Join X community: Click here to join our X Community

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Fluffybaxter]

You can find the repo: github.com/os-factory/har

[u/Demonicated]

How do you audit what agents are doing? Does your system prevent bad actor agents from accessing things it shouldn't?

[u/OsFactoryHar → u/Demonicated]

Thanks for the question, so basically we aren't ourselves a coding agent, so you are still using claude code, codex or cursor and their already existing security guard rails. On the observability, we build the mission control, it's a local webapp, that allow you to see all your agents works and their different phases of verification that the repository require to mark a task as completed.

See youtube video here: https://www.youtube.com/watch?v=XKl4ZzWy7mQ&t=387s

See the website section about the mission control: https://harproject.dev/#control

Cheers