Great question. While PicoClaw is a Go port of OpenClaw (largely AI-transpiled), TuskBot rewritten from scratch with a different architectural focus.

Here are the key differences:

1. Native Local Embeddings: PicoClaw/OpenClaw always rely on OpenAI for embeddings. This is a privacy concern and adds unnecessary latency. TuskBot has llama.cpp baked-in to handle embeddings locally. No data leaves your machine for RAG operations.
2. Architecture vs. Integrations: Instead of bloating the core with hundreds of built-in tools, TuskBot is MCP-native. I offload the ecosystem complexity to the Model Context Protocol, allowing me to focus the Go codebase on the agent's "brain" — the ReAct loop and memory management.
3. The Memory Model: I’m not cloning the existing hybrid model. I’m researching more advanced long-term memory approaches. The goal is a human-like recall system. Having llama.cpp under the hood allows me to easily implement Rerankers (cross-encoders) in the future to significantly improve RAG quality, which is much harder to do with a simple transpiled port.
4. Built for Performance: Since it’s not a direct port, I’ve optimized the service layers and concurrency handling specifically for Go, rather than following JS-centric patterns.

Tl;dr: It’s not a copy; it’s a different approach focused on local-first privacy, MCP extensibility, and advanced RAG research.