[flagged]
Headlong: A microharness for persistent agents
61–67 of 67 posts
Re: Headlong: A microharness for persistent agents
#62Earlier quoted context omitted.
We need "React" moment, to solve imperative O(n^2) state transitions with declarative O(n) target states, and let the harness do the "diffing"
I literally just wrote about exactly that https://nicktrevino.com/your-repository-is-your-swarm.html
> bingeineering
i'm gonna start using this
Re: Headlong: A microharness for persistent agents
#63Earlier quoted context omitted.
I'm curious, you say "super interesting engineering" but then they say "it will often just tell you, even though we’ve asked it not to" and to me that seems like extremely shit engineering. Where are the interesting engineering parts at? Seems to be an interesting idea and perhaps design, but to call the implementation/engineering itself bad seems to be an understatement.
Good engineering means optimizing the things you care about, at the cost of things you don't. In this case, secrecy doesn't matter kinda inherently. It's like criticizing Reddit for not handling SSNs well; the intended design is 'just don't do that, cause you'd never have a reason to, anyway'
If secrecy doesn't matter, why did they tell the agent not to divulge stuff in the first place?
Re: Headlong: A microharness for persistent agents
#64Earlier quoted context omitted.
Don't use any public benchmarks, every single one is worthless for your own use cases essentially. Spend a day or two going through your existing chat sessions, and create your own private benchmark with test cases based on real tasks, that you don't share with anyone nor publicly. Make it easy to add/remove new harnesses and model combinations, make it give you a final score, ideally avoid using other LLMs for scori…
> make it give you a final score what does this mean exactly? A scored based on what?
For translations, the score is basically 1 or 0. For some tasks, the least amount of LOC gives the highest score, and so on. Basically, you need to figure out how to score it, so you can compare scores across agents/models.
Re: Headlong: A microharness for persistent agents
#65Earlier quoted context omitted.
You can always read the script file (orm ore realistically feed it to agent). If they distributed appimage or rpm would that be safer anyhow? Cannot it run malitious code same as the script would run?
One of the big problems is that no one actually does read these scripts. You could say "Oh but it's their own fault, duh" but theres a very legitimate argument to be made users going the path of least resistance and that you shouldn't offload this responsibility on your users. Regarding appImage or rpm, attackers need to build and package these to inject these, while this curl | bash pipe opens up the possiblity of p…
> no one actually does read these scripts
I do.
Re: Headlong: A microharness for persistent agents
#66The Googlers must be vague posting about something internal.
Your comment is also rather vague, how is it relevant? Did you observe something interesting?
Re: Headlong: A microharness for persistent agents
#67[flagged]