Earlier quoted context omitted.
How do you view harness engineering as an organic development that emerges from its use within a specific domain? Basically the meta-loop that allows an agent to tailor its harness to improve outcomes based on performance feedback. I use Pi a lot and I'm very interested in "self-assembling software". One concrete example might be maintaining a conventions document per-project that covers how to name things semantical…
Your example is super amenable to vibing some tests. As an example, I’ve been able to ban `number` from representing a duration by walking the AST in a linter to fail if var or param names that look like the end in millis or ms or sec appear. This is largely good enough. If you see that “drifting” behavior appear more than once, you have enough to stop and force the agent to write some static verifiers that reject al…
Harness Engineering
11–20 of 39 posts
Re: Harness Engineering
#12Re: Harness Engineering
#13Hi folks, author here and also author of the seminal OpenAI blog on this topic. Let me know how I can help you all let it rip.
"When a quote sounds profound enough, reality usually nods out of politeness, without echoes is just a sentence wearing pajamas." - slopinthebag
Re: Harness Engineering
#14[flagged]
Re: Harness Engineering
#15Hi folks, author here and also author of the seminal OpenAI blog on this topic. Let me know how I can help you all let it rip.
Re: Harness Engineering
#16Hi folks, author here and also author of the seminal OpenAI blog on this topic. Let me know how I can help you all let it rip.
Thanks. I am guessing you have to try stuff and build tacit experience. No other way, just get stuck in and try stuff, then try and learn bits from others?
Re: Harness Engineering
#17Earlier quoted context omitted.
One challenge/opportunity I've had is harnessing really wide running cheap agents. Any thoughts on how to move really cheap agents beyond basic summarization so we can go broader than the pricing of frontier llms allows?
Your “really cheap” agents can’t be so cheap that they do not have good tool calling skills. But! Using bigger models to put guardrails in place as static verifiers allows lower complexity changes to “self steer” as tests fail, which means coming down on the cost curve is more effective.
So $1.5 for 40m tokens I guess would cost much more with sota (but would need less tokens perhaps).
Re: Harness Engineering
#18Hi folks, author here and also author of the seminal OpenAI blog on this topic. Let me know how I can help you all let it rip.
What motivated you to quote your own quote (??) in your readme claiming to boost productivity by 100x, and where did you derive that number from? "When a quote sounds profound enough, reality usually nods out of politeness, without echoes is just a sentence wearing pajamas." - slopinthebag
Re: Harness Engineering
#19Hi folks, author here and also author of the seminal OpenAI blog on this topic. Let me know how I can help you all let it rip.
Thanks. I am guessing you have to try stuff and build tacit experience. No other way, just get stuck in and try stuff, then try and learn bits from others?
Re: Harness Engineering
#20> A command can feel ambient without making its credential model-visible.
I'd be wary of following guidelines on how to build human-computer interaction systems that weren't written with full human oversight. This kind of wording makes me wonder if these are actual recommendations or just the AI pattern-matching and hallucinating something that looks coherent.