@rob_vb
Great question, Rob! They basically solve different problems.
Cloud Code’s agent teams. Configured by a single lead agent – the lead decides which subtasks to assign, create workers, and integrate their output. This is top-down coordination. The lead agent knows about all workers because it created them.
SLM solves the anti-mesh problem. – What happens when you have free Sessions that didn’t originate from the same lead? For example:
You open Claude Code in VS Code to work on the front end.
You open another cloudcode session in your terminal for the backend.
Your partner opens a cursor on the same repo.
You have Antigravity running with Gemini for the third task.
These sessions are Zero awareness of each other. They can’t share context, coordinate file edits, avoid stepping on each other. You become a message bus – copying and pasting context between terminals.
The SLM mesh adds a communication layer between these independent sessions:
Peer discovery – “Who else is working on this machine/repo?”
File locking – “Don’t modify auth.ts, someone else is refactoring it”
Messaging – “I just updated the database schema to v2.1”
A common state – A key-value store all sessions can read/write.
The ceremony is over – Subscribe to changes in real time.
Works with it. anyone MCP-compatible agents — Claude Code, Cursor, Windsurf, Aider, Codex — even in different AI models. In our demo video, Claude and Gemini are talking to each other through Mesh.
Under the hood: A lightweight broker starts automatically on localhost (SQLite + Unix Domain Sockets for <100ms delivery). Bearer Token Authentication. Closes automatically when no sessions remain. 480 tests, 100% coverage.
Think of it this way: Cloud Code teams are like a manager who assigns work to direct reports. SLM Mesh is similar to Slack – it allows independent people (or agents) to work on the same thing without a central manager.
SLM stands for Super local memory – Native-first AI memory system. If SuperLocalMemory is the brain (persistent memory), SLM is the mesh neural system (real-time communication wires between agent sessions). They are part of both. Qualixar Research initiative