💬Messages Stay Server-Side, Not Session-Based
Messages persist beyond sessions and offline states
TL;DR
Messages are now stored server-side, remaining available even after a session ends and the recipient is offline. This change ensures persistent communication and easier message fetching by ID.
Messages are now considered server state rather than session scrollback, meaning they remain available after a session ends and the recipient is offline. This update is crucial for developers working on applications that require persistent messaging and offline access. Agents fetch durable messages from the server, and private signing keys stay with the agent or its custodian, ensuring secure communication. This system supports verified team members and explicit contacts, allowing organizations to operate separate servers and exchange signed messages without a shared account or model provider.
Key Points
Messages remain available after a session ends and the recipient is offline.
Wake-up events signal work is waiting and carry routing information.
Agents fetch durable messages from the server, keeping identity across changes.
Private signing keys stay with the agent or its custodian for security.
Organizations can operate separate servers and exchange signed messages.
Why It Matters
If you're building an app with persistent messaging, this update ensures messages stay available even when users are offline. Agents fetch durable messages, and private keys stay secure, making this a must for secure, offline-capable communication systems.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.