Great idea and name the danger here which I'll be interested to track is how do you keep this "nano"? Since it's built for you, you'll continue adding features i assume which over time will make this not very nano. I guess I'm wondering if there could be some small design tweaks of the repo that make this usable as a long term "fork the base and make it your own" concept
I will keep the source code as a minimal implementation that has the core capabilities that made Clawdbot/OpenClaw useful: chat with it via messaging app (only one channel included out of the box), memory (minimal implementation that leverages CLAUDE.md and the filesystem), cron jobs, browser.
If I want to add additional capabilities for myself, I'll contribute them to the project as skills for claude code to modify the code base, rather than directly to the source. I actually want to reduce the size of the base implementation and have a PR open to strip out 300-400 LOC
It makes me chuckle every time the state changes lol. But by making it configurable hopefully it can actually be a useful feature for people (fingers crossed)
It’s Sunday night/Monday morning, I just got back from a great day at FOSDEM 2026, and since I’m on the east coast time schedule, might as well tackle some outstanding issues on agent-of-empires.
Step 1, backlog prioritization.
Step 2, realize that truly the most important thing the tool is mising is AoE sound effects.
Step 3, add configurable sound effects.
Now you can optionally enjoy being told “wololo” when Claude needs to you to confirm your plan before executing the implementation. Enjoy.
Go to docs to see how to install the open source sounds (the internet can show you how to grab the real aoe ii sounds, because of copyright concerns I didn’t bake it into the codebase).
Excited to finally be able to give this a try today. I'm documenting my experience using aoe + OpenCode + LM Studio + GLM-4.7 Flash + Mac Mini M4Pro 64GB Mem on this thread if anyone wants to follow along and or give me advice about how badly I'm messing up the settings
I had the same experience using smolagents. Early 2025 it was a competitive approach, but a year later having a small subset (<10) of flexible tools is outperforming the single-tool approach.
Nathan here: Anushri and I wrote this after many discussion in our team here at mozilla.ai. Not only from experiences managing contributions in our own OSS code but also in extenral OSS codebases we contribute to ourselves: we've seen varied methods for handling AI usage when it comes to contributions.
Hopefully this post helps kickstart the discussion about what we should do to help keep OSS codebases a wonderful place to contribute and learn from each other.
Regardless of how you feel about AI generated code, we think it's crucial that we talk and learn from each other. AI Coding is a new world and it's here to stay, learning from each other about how to navigate learning and optimizing our new skill sets is important.
reply