Just tried. And wow!! I opened my mac's activity monitor to see how much load it was putting on my system, and i had to scroll all the way down ... unlike those current harnesses that sit right on top (sorted by used cpu, descending).
And it worked. I'm switching to this unless i find a reason not to.
Yeah, using it a bunch with local LLMs. It's fast (small system prompt), focused on the basics, made around simple choices, and possibility to call it in scripts.
So far I have very positive experiences, the results are generally better (and not just faster) than in other harnesses with the same models. I've done the same (user) prompts for tasks in a range of them, and compare the outcome to eval between them. Simple (harness) beats complicated one many times. I do wish it could use MCP though, but not as often as I think, and CLI tool usage often compensates on this front with little extra effort)
That is now my usuall go-to harness for things usually. Still figuring out the edges though (when we get off the happy path, like models reaching their max context, or such...)
It's very light, recommed you try it out, and see if it fits your toolbox.
That landing page is hard to look at, let alone read. Have LLMs really not yet learned to write webpages that read the sytem theme and look that way? Must be hard.
it's minimal and somewhat opinionated, not integrated well with memory subsystems (although that's kind of the point)
my only real criticism is that last I played with it it deals with slow provider responses very poorly , so lots of locally hosted llms require a lot of tuning to get it to handle streaming/non-streaming/timers well.
way less minimal (but still pretty minimal) I prefer Pi; but different markets I think.
hax fit my openbsd laptop well, espescially since Pi and related derivatives are kind of un-spokenly incompatible with the BSDs.
(author passing by) Could you please report the issues you've experienced on the repo? I did quite a bit of testing myself on local models (Qwen, Ornith, Gemma, Muse Glimmer) with llama.cpp, and they all worked fine. Details would be helpful.
Also one brief note for Codex users specifically. hax can work out-of-the-box as codex-cli drop-in replacement (since it can use the already authenticated codex token), so it's super easy to try it - basically it will be a zero-config experience.
Just tried. And wow!! I opened my mac's activity monitor to see how much load it was putting on my system, and i had to scroll all the way down ... unlike those current harnesses that sit right on top (sorted by used cpu, descending).
And it worked. I'm switching to this unless i find a reason not to.
Yeah, using it a bunch with local LLMs. It's fast (small system prompt), focused on the basics, made around simple choices, and possibility to call it in scripts.
So far I have very positive experiences, the results are generally better (and not just faster) than in other harnesses with the same models. I've done the same (user) prompts for tasks in a range of them, and compare the outcome to eval between them. Simple (harness) beats complicated one many times. I do wish it could use MCP though, but not as often as I think, and CLI tool usage often compensates on this front with little extra effort)
That is now my usuall go-to harness for things usually. Still figuring out the edges though (when we get off the happy path, like models reaching their max context, or such...)
It's very light, recommed you try it out, and see if it fits your toolbox.
That landing page is hard to look at, let alone read. Have LLMs really not yet learned to write webpages that read the sytem theme and look that way? Must be hard.
it's okay.
it's minimal and somewhat opinionated, not integrated well with memory subsystems (although that's kind of the point)
my only real criticism is that last I played with it it deals with slow provider responses very poorly , so lots of locally hosted llms require a lot of tuning to get it to handle streaming/non-streaming/timers well.
way less minimal (but still pretty minimal) I prefer Pi; but different markets I think.
hax fit my openbsd laptop well, espescially since Pi and related derivatives are kind of un-spokenly incompatible with the BSDs.
(author passing by) Could you please report the issues you've experienced on the repo? I did quite a bit of testing myself on local models (Qwen, Ornith, Gemma, Muse Glimmer) with llama.cpp, and they all worked fine. Details would be helpful.
Also one brief note for Codex users specifically. hax can work out-of-the-box as codex-cli drop-in replacement (since it can use the already authenticated codex token), so it's super easy to try it - basically it will be a zero-config experience.
Thanks for making it :)