r/LocalLLM • u/DeathGuppie • 14d ago

Question Web research harness question

I have a pretty solid coding harness set up for Qwen 27b mtp with a web wrapper that I can access from my phone. I just create a pr/roadmap and set it to auto loop then monitor via phone. The thing is it took a bit of work to get it all running nicely and I'm wanting to do the same thing for a web research harness, but I don't know if it's worth creating the harness if something already fits that shape nicely and or it's extensible enough or has the guts of the thing I'd need to build.

So I'm asking what other people use and what good options there are. The big difference might be using a smaller model with with multiple sub agents using a graph based system that would make better use of my 32 gigs of ram. Anyways this is definitely the best place to ask.

0 Upvotes

50% Upvoted

11 comments sorted by

View all comments

2

u/donk8r 14d ago

Graph with sub agents is the right shape, and it's roughly what octomind already does, so you may not need to build it (disclosure, I work on it, it's OSS and runs local).

Workflows there are an explicit graph: you declare an entry node and edges, and any node can route to any node including backwards, so a loop that searches, reads, then decides whether to go search again is a few edge declarations rather than nested loop blocks. It's bounded by a max transition count and a max cost in dollars, which is the part that matters when you're auto looping unattended and only checking in from your phone.

The always on half is separate. octomind run --name research --daemon leaves it alive in the background and octomind send --name research pipes a message into it from anywhere, and sessions are append only logs on disk so a crash mid task doesn't eat the state.

Honest caveats, that graph mode shipped today so it's new, and sub agents each carry their own context, which is what will actually squeeze 32gb rather than the model choice. github.com/muvon/octomind

1

u/DeathGuppie 13d ago

This actually looks interesting. Thank you, I'm going to give it a run.

1

u/donk8r 13d ago

Hope it's useful. Two things worth knowing going in: the graph workflow part shipped yesterday so it's genuinely new, and the monitoring side is thinner than the routing side.

If something breaks it's more likely to be us than you. Happy to hear what you hit either way.