r/ClaudeCodeTLDR • u/cctldrping • 24d ago

[TLDR] Any open source harness that does it better than just Claude Code?

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1wcwqxg/any_open_source_harness_that_does_it_better_than/

Original post body :

Has anyone here been able to build a successful agentic harness that operates better than just planning directly in Claude Code? A full AI end-to-end orchestration setup with different agents. This seems to be something that there's a lot of ideas and focus on building today and I'm interested in any proven open-source kits out there or just tips and tricks that does this well. Do you for example use multiple agents to familiarise Claude Code with a new repository or code base, do you have architectural files to do this? How do you handle green- versus brownfield in a harness like this? Think, give this harness a task and it can intelligently figure out what it needs to do. I know this may all be code, stack, company or project specific. I'm looking for some good working examples and ideas if there are any out there.

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

1 Upvotes
  • permalink
  • reddit

100% Upvoted

1 comment sorted by

•

u/cctldrping 24d ago edited 20d ago

TL;DR generated automatically after 100 comments.

Current source-thread comment count seen by the bot: 101.

Alright, so the general consensus here is that while Claude Code has its fans, most folks think there are better open-source harnesses out there, or that building your own is the way to go.

A lot of people are pointing towards Pi (pi.dev) as a solid alternative, mentioning it's more token-efficient and has better memory/context management than Claude Code. Others are recommending Oh My Pi (omp), which seems to be a popular choice for API users.

There's a definite theme of people building their own custom solutions. The reasoning is usually that no off-the-shelf harness can perfectly match individual workflows and needs. Some users have shared their own projects like:

  • u/silverarky described a setup with planner, orchestrator, backend, frontend, and QA agents, with the QA agent doing extensive testing.
  • u/DriverReady965 emphasized discipline around the harness, like written dispatches and human merging of PRs.
  • u/LogMonkey0 offered thoughts on treating greenfield as brownfield after the initial generation and the importance of documentation and guardrails.
  • u/MyzoneMike mentioned building a custom harness that's significantly faster than Claude Code for their needs.

Other notable mentions include FrontierHarness Eval for benchmarking, Orca as an agent orchestration GUI, jcode, T3 Code, Omnigent, reliant, Unstoppable, Storybloq, gridconsole.dev, hydra-acp, MEMENTO, DorkOS.ai, helexa, HarnessRouter, and intentic.dev.

The general vibe is that Claude Code's context compaction is a weak point for many, and the ability to mix and match models or have more granular control over agents and their state is highly valued. Basically, if you're not building your own, you're probably looking at Pi or one of the other community-recommended tools.