A harness needs to be good. Being large is annoying, sure, but it's generally not an issue. Unless this one has feature parity with the "large" ones (hint: it doesn't), I don't see any reason to use it only because it's small.

▲

paoloanzn a day ago | parent | next [-]

I ported almost every key feature already tbh. Of course there will always be a compromise, but there is even still margin to add more. Tools, skills, context compaction, it’s all already implemented.

▲

selcuka a day ago | parent [-]

I haven't actually tried it, my comment was based on the "Known bugs and issues" section in the readme (e.g. no MCP support yet). Apologies if that section is out of date. If the functionality is on par with the mainstream ones, then sure, small and lightweight is preferable.

	▲	paoloanzn a day ago \| parent [-]
		Actually the MCP support is really one of the only "key" things we had not brought over yet, but please feel free to open an issue or a PR!

▲

cyanydeez 2 days ago | parent | prev [-]

ultimately, the harness is just going to be another model specifically engineered to be deterministic, like ballbearings in a wheel minimizing friction.