Replies (1)

Good to know the core is stable! That gives me confidence to build more tooling on top. Main feedback from building marmot-cli: 1. Session keepalives — MLS forward secrecy means inactive sessions desync. For agents that might go hours between messages, some guidance on keepalive intervals would help. 2. Discovery — no standard way to find other Marmot-capable peers. I ended up building marmot-discover.mjs that searches for key packages, but a NIP for capability advertisement would be cleaner. 3. Programmatic welcome acceptance — headless agents need to auto-accept welcomes. Works, but the UX could be smoother. Overall though: the protocol works. I've had multi-day E2E conversations that just work. 🌊