logoalt Hacker News

ernsheongtoday at 1:29 AM6 repliesview on HN

I built my harness in pi within herdr, I cloned (zipped and downloaded) 0xRichardH/pi-herdr-subagents and went from there, and used pi to build itself, adding gate workflow state control, provider fallbacks (I use many token plans), subagent skill injection, etc.

It is highly custom to my needs and wants, and I think every developer needs to do this. I only talk to my planner which plans, and it subs out to designer, oracle, coders, testers, and reviewers, etc. It is thus highly optimized for correctness. You can TDD or no TDD. You can fast track small changes. I tweak my harness dozens of times as I encounter new edge cases (esp when I switch models and encounter models not as good at following instructions).

As you can start to see, it is better to own the harness because nobody can build something custom that 100% fits your needs or development philosophy.


Replies

Bockittoday at 10:01 AM

I cannot agree more. We all have our own needs, and it’s never been easier to make something that meets them exactly.

I have been running my own setup and evolving it since November as I come up with more ideas and needs. The nicest bit is not being tied to one provider or another. Anthropic decides to stop supporting Claude agent sdk with subs? Or astra outstrips other models? My harness now works with Claude/cursor/codex and soon ACP. It didn’t start that way, it was originally all in on Claude, but now all the things I built on top of Claude now work with the others too.

tokioyoyotoday at 4:47 AM

Correct me if I'm wrong, but the harness will always be dependent on the underlying model, and useless without it. All custom harnesses are being built, could be obsolete in the next big-generation-jump of the models.

I might be absolutely wrong, but "harnesses" / cc-derivatives became "good enough" only maybe a year ago max. Before that, people were pushing for gigantic folder structures with custom documents and "pretend you're X" stuff.

My point is, depended on what you're trying to achieve, testing out current-gen harnesses, and nudging your workflows towards them might be better RoI, rather than chasing something that might be throwaway code a quarter later.

Obviously, this really depends on whether you believe model development will speed up or slow down in the upcoming future.

show 4 replies
durdntoday at 8:06 AM

I did a similar thing, took those sub agents primitives and ran with it: https://github.com/durdn/herdr-interactive-subagents I do still use more than one harness though.

dsrtslnd23today at 7:58 AM

I also built a custom harness tailored to my needs using pi.dev underneath. From time to time I use the 'official' harnesses of openai/anthropic but can't confirm that they are much better adapted to that harness.

_davide_today at 8:37 AM

100% every professional developer at some point should build its own harness as daily driver

boredtofearstoday at 4:06 AM

I'm very interested in this but I am confused on what Pi provides you if you are building the harness? What does Pi get you that writing from scratch doesn't?

Any good starting points or tutorials you recommend?

show 1 reply