slm-mesh

# slm-mesh — Cross-Session Peer Coordination The mesh network lets multiple AI agent sessions on the same machine discover each other and coordinate in real time — without writing to the persistent memory store. Mesh messages are transient (48-hour TTL); they complement memory (which is durable) rather than replacing it. Mesh is local-only: it uses the SLM daemon as a local broker. No data leaves the machine. --- ## Profile requirement Mesh tools are available in the `full`, `power`, and `mesh` MCP profiles. Confirm the active profile with `slm status` before calling mesh tools. If the tools are not available, switch to `full` profile with `switch_profile("full")` (requires `code` or higher active profile). See `slm-profile`. --- ## Tool reference ### 1. `mesh_summary` — announce what this session is doing ``` mesh_summary(summary: str = "") -> dict ``` Call at session start to register on the mesh and announce your purpose. Other sessions can see your summary via `mesh_peers`. The session stays alive via automatic heartbeat. ``` mesh_summary(summary="Refactoring auth module in api/src/auth/") ``` Response: `{peer_id, summary, project_path, registered, heartbeat_active, broker_response}` Call this once at the start of any session that will participate in the mesh. The peer registration happens automatically at MCP startup, but calling `mesh_summary` sets the human-readable description that other agents see. --- ### 2. `mesh_peers` — list active sessions ``` me...