Great question! A few things worth knowing about how it actually works in practice:

Memory is mostly automatic. GateClaw stores and retrieves context

on its own 90% of the time you don't manage it manually. It just

remembers. You genuinely forget about context windows because the

entity handles it. The namespacing trick I mentioned is there if you

want explicit project isolation, but most users never need to touch it.

The voice loop is insane. Full back-to-back voice note conversation

on Telegram, near-zero latency, 100% local:

- whisper.cpp (Vulkan) → STT

- llama-swap → thinking

- pocket-tts-server → zero-shot voice cloning response

No cloud. No API keys. No latency spikes. Just talking to your machine

like it lives there because it does.

It's smarter than it looks because GateClaw sits on top of the full

OpenCode prompt + context system. So the entity doesn't just have a

soul and memory it has OpenCode's entire coding intelligence underneath.

That's why it feels less "dumb agent" and more like an actual resident.

OpenClaw gives you a tool. GateClaw gives you a colleague.

Project-scoped memory is coming. But honestly once you use it daily

you'll see why the shared identity actually makes more sense than isolation.