Is there an accepted definition on what a harness is? Is this like GasTown and similar? Plan mode? Is this a client-side loop with multi-threaded agents running in parallel? If the AI client is doing this on its own, is that considered agentic and/or using a harness? Or does the introduction of saving text to a MD file make it "self learning" a harness?
It feels like the pace at which the industry is defining things may be faster than the actual pace of change sometimes.
Not currently, but I probably will be in the coming weeks.
I pretty much end up hating every harness I use. Some come really close to what I'm looking for but then completely miss the mark in other ways. At the moment, I'm stripping OpenCode down to its absolute bare minimum, removing pretty much all of the vendor-specific crap and everything else I don't plan on using. Once I'm convinced that's stable, I'll identify how all the "good parts" work and reimplement the core using Rust.
And yeah, I know Pi exists, which in many ways is what I'm looking for, except even that ended up being more of a bulky mess than what I was hoping. Chose the install with Homebrew option, and for some reason it took an ungodly amount of time to install a buttload of dependencies and then compile, only to completely stall out and fail. I mean... what the fuck. Glad it works for other people, but this is the exact type of total nonsense that I'm done with when it comes to modern software.
For Pete's sake... I just want something that reads my text, contacts an LLM, and runs commands on my system. Why does this have to feel like coordinating a manned mission to the Moon? This shouldn't require even hundreds of megabytes of a runtime. It takes a fraction of the time for me to compile the Perfect Dark PC Port, a full blown FPS game, than it does for me to install some of these harnesses.
I'm curious to hear what the problem was with Pi? I'd assume the problems you mentioned are due to homebrew (and its dependency churn) rather than Pi itself.
I have been using my own harness for quite a while now and giving it constant and continuous updates and improvements. It is optimized for use with local models but can also use any API that I have an account with too when the desire arises.
I've only implemented support for one provider at the moment, but it is structured in a way where I can add support for any other providers or local models. It feels good to not be locked into any one company's models or harness.
Yeah, I built mine to learn how these work and have been playing with it since then while I look for a job. https://github.com/devoidfury/hotdog
Is there an accepted definition on what a harness is? Is this like GasTown and similar? Plan mode? Is this a client-side loop with multi-threaded agents running in parallel? If the AI client is doing this on its own, is that considered agentic and/or using a harness? Or does the introduction of saving text to a MD file make it "self learning" a harness?
It feels like the pace at which the industry is defining things may be faster than the actual pace of change sometimes.
Not currently, but I probably will be in the coming weeks.
I pretty much end up hating every harness I use. Some come really close to what I'm looking for but then completely miss the mark in other ways. At the moment, I'm stripping OpenCode down to its absolute bare minimum, removing pretty much all of the vendor-specific crap and everything else I don't plan on using. Once I'm convinced that's stable, I'll identify how all the "good parts" work and reimplement the core using Rust.
And yeah, I know Pi exists, which in many ways is what I'm looking for, except even that ended up being more of a bulky mess than what I was hoping. Chose the install with Homebrew option, and for some reason it took an ungodly amount of time to install a buttload of dependencies and then compile, only to completely stall out and fail. I mean... what the fuck. Glad it works for other people, but this is the exact type of total nonsense that I'm done with when it comes to modern software.
For Pete's sake... I just want something that reads my text, contacts an LLM, and runs commands on my system. Why does this have to feel like coordinating a manned mission to the Moon? This shouldn't require even hundreds of megabytes of a runtime. It takes a fraction of the time for me to compile the Perfect Dark PC Port, a full blown FPS game, than it does for me to install some of these harnesses.
I'm curious to hear what the problem was with Pi? I'd assume the problems you mentioned are due to homebrew (and its dependency churn) rather than Pi itself.
omp (oh-my-pi) all the time. I just loved embracing the terminal and being able to switch between providers freely.
I have been using my own harness for quite a while now and giving it constant and continuous updates and improvements. It is optimized for use with local models but can also use any API that I have an account with too when the desire arises.
I've only implemented support for one provider at the moment, but it is structured in a way where I can add support for any other providers or local models. It feels good to not be locked into any one company's models or harness.