The emails go through quickbooks/accounting software, Clawbolt doesn't have any direct email client. Use of tools is on a gradual permission basis like Claude code, and Clawbolt doesn't have any general code access or web access. I think you highlight an important point though that prompt injection continues to be a hazard of AI agent use, though tools continue to be developed to fight against it. The goal is to lock Clawbolt down as much as possible to help users avoid the security hazards of systems like openclaw, but this is definitely something that we'll need to watch and be careful about!
Thanks for the response, I have family in the construction industry and if i introduce a tool like this to them and they get hacked or some dumb stuff happen they will not be happy. But its very cool and I think a lot of the tickytacky computer work does get in the way of the business so this seems like a good direction to go
Nathan here, MLE at Mozilla.ai. We wrote this because the AI productivity conversation has been almost entirely about desk workers, and we think that's a miss.
My buddy runs a general contracting business. He's good at what he does, but he spends a lot of evenings on a laptop chasing invoices and scheduling follow-ups instead of hanging outwith his family and friends. Most tools being built right now weren't built primarily for him.
Clawbolt is our attempt at a purpose-built AI assistant for people in the trades. It lives in messaging apps they already use, connects to things like QuickBooks and Google Calendar, and is proactive rather than waiting to be asked, just like OpenClaw. Following up on unpaid invoices, flagging material cost changes, that kind of thing. Open source core at github.com/mozilla-ai/clawbolt if you'd like to check it out and give it a star.
We're early and looking for input from people who actually work in the trades or run small trade businesses. Would love to hear what resonates and what we're missing.
I am building something similar in the UK. As a contractor, I have to manage tax, invoices, reconciliation, payroll, accountant emails.
I think software in the future will be general portals which roughly self manages via plugins and automation. Services like QuickBooks will eventually just be an MCP server and you can tailor the software as you wish.
Very cool! Quickbooks is an interesting area because imo it's so important to be super super careful with how that interaction model works. Narrowing on a very specific vertical like small business contractors I think should help to make sure that we can nail the interaction model to make it easy and safe.
Glad to hear it! oooh interesting, I've seen worktrunk but haven't explored it too deeply yet.
The sounds are sort of an easter egg: you can enable/disable them from the settings page (hit 's' in the TUI). You probably are experiencing them being random because the default is to select "random" sounds (see the settings TUI screen). I don't use the sounds much so I'm waiting for a contributor to suggest an improvement.
It's the wonderful part about OSS and 'mission-driven' projects. If the mission is not to make money, then a project is free to reject addons/etc that might be lucrative but not add value to the core of the product
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).
