nanobot

I can’t speak to the veracity of the benchmarks but it appears their methodology is sound. Nanobot has 47k stars, fwiw https://github.com/HKUDS/nanobot It has been more of an OpenClaw or Hermes alternative than a coding agent like OpenCode or Pi, so it’s likely to do well given less context bloat.

Hey - I'd love for you to add a documented / standard way to use this inside dockers so we can use build on it for various agentic efforts. I've solved getting bubblewrap to work inside a docker once for the nanobot project, but the folks there are dragging their feet on incorporating sandboxing. https://github.com/HKUDS/nanobot/pull/1940

I'm surprised to see nanobot uses LiteLLM: https://github.com/HKUDS/nanobot LiteLLM wouldn't be my top choice, because it installs a lot of extra stuff. https://news.ycombinator.com/item?id=43646438 But it's quite popular.

> don't understand that those abilities have been around for a while now Hugely underestimated comment. That's pretty much the entire point here. Many people didn't know something with these capabilities was already possible. Or some - like me - knew of the potential, but couldn't be bothered/didn't have the time to put the bits together in a satisfactory flow (I'm currently exploring and building on nanobot[0], which is directly inspired by OpenClaw; didn't touch OC because it's in JS and I'm a Python person). Everything came together really well, which is why it's a "killer app". And now the dam has burst there will be customized takes on the concept all over the place (I'm also aware of a Rust "port", Moltis[1]), taking the idea to next levels. [0] https://github.com/HKUDS/nanobot [1] https://github.com/moltis-org/moltis

As you mentioned, that depends on what you mean by planners. An LLM will implicitly decompose a prompt into tasks and then sequentially execute them, calling the appropriate tools. The architecture diagram helpfully visualizes this [0] Here though, planners means autonomous planners that exist as higher level infrastructure, that does external task decomposition, persistent state, tool scheduling, error recovery/replanning, and branching/search. Think a task like “Prompt: “Scan repo for auth bugs, run tests, open PR with fixes, notify Slack.” that just runs continuously 24/7, that would be beyond what nanobot could do. However, something like “find all the receipts in my emails for this year, then zip and email them to my accountant for my tax return” is something nanobot would do. [0] https://github.com/HKUDS/nanobot/blob/main/nanobot_ar