𝗜 𝘁𝗲𝘀𝘁𝗲𝗱
@bot 𝗮𝗻𝗱
@Muse 𝘀𝗶𝗱𝗲 𝗯𝘆 𝘀𝗶𝗱𝗲, 𝗮𝗻𝗱 𝗱𝗿𝗲𝘄 𝗯𝗼𝘁𝗵 𝗵𝗮𝗿𝗻𝗲𝘀𝘀𝗲𝘀 𝗯𝘆 𝗵𝗮𝗻𝗱.
One from
@SpaceXAI, one from
@AIatMeta under
@alexandr_wang. Neither is open source, so I tried both and drew the architecture myself from whatever docs exist. Tbh I struggled quite a bit to find real use cases that can surprise me beyond what we have on Claude Code and Codex, but maybe we are just getting started on personal agent harnesses.
🌟 Github Repo (1.8k):
github.com/ShenSeanChen/waku…
💻 Portable memory:
waku.one
☕ Join our community:
seanchen.io
Some quick differences I found:
Grok Bot gives your whole account one cloud VM where every Bot shares the browser, the /workspace, the terminal and the credentials, so a Bot is isolating a personality rather than a context.
Muse gives each person one secure VM with a single agent, and a Sentinel sitting outside the container holding your tokens.
Strip the branding off either one though and it's the same chain:
one VM → connectors → routines → approval gate → memory
What surprised me is that Muse ships a memory.md you can read, edit and download, but Grok Bot doesn't. I didn't find where it keeps memory at all. So I gave both of them
@waku_agent memory over MCP instead, saved a fact in one harness, and the other one recalled it cold in a fresh chat.
I also killed the shopping test halfway. I felt Amazon was built for humans to read and click, and I wasn't handing an agent my login username and password. Maybe the fast checkout use case is a better fit for software / AI product purchases.
Watch it, then save both harness diagrams below. 🔖
You Can Build Anything. You Can Learn Anything. 💪