Using namespaces to manage multiple projects from a single OpenClaw agent

If your OpenClaw agent works on more than one project, you have a problem. Memories from project A leak into recalls for project B. You ask about deploying the frontend and get back memories about a completely different repo's CI pipeline. Everything is in one pile. MemoClaw namespaces fix this. A namespace is just a label that isolates a group of memories. Memories in namespace project-a won't show up when you recall from project-b . Simple concept, but the strategy around how you use them matters. How namespaces work Every MemoClaw operation accepts a --namespace flag. If you don't specify one, memories go into the default namespace (empty string). # Store in a specific namespace memoclaw store "Frontend uses Next.js 14 with app router" \ --namespace website-redesign --tags "stack" # Recall only from that namespace memoclaw recall "what framework are we using" --namespace website-redesign # List memories in a namespace memoclaw list --namespace website-redesign # See all your namespa