Messaging while offline

After Monad has synchronized your workspace on a device, you can reopen your last route without a connection and switch among cached spaces and DMs. Their real headers and recent messages come from the device; Monad does not wait for a network request before showing them.

What you can do offline#

• Send, edit, or remove a text message.
• Reply in a thread, including starting the first reply.
• Add or remove a reaction.
• Share an existing message to another space, or remove one of its shared placements.
• Advance read positions as you browse.

These changes appear immediately and are stored on the device before Monad tries to send them. Each conversation has its own queue, so a blocked change in one channel does not stop another channel from syncing.

Attachments and file changes require a connection. If files are selected, Monad asks you to remove them before sending offline. Creating spaces, inviting people, and other administrative changes are also online-only.

Reconnecting and older changes#

Monad retries recent queued changes automatically and applies each one only once, even if a response was lost or another tab also retried it. If the server rejects a change because access changed, the cached view is restored to the authorized server state.

After a queued change is more than an hour old and the app has been relaunched, Monad asks what to do: Send now, Edit (for queued text), or Discard. At 24 hours an unsent change is marked failed instead of retrying forever.

Offline access is for a device that was previously signed in and synchronized. Permission or session revocations that happen while the device is fully offline take effect when it reconnects; revoked cached data is then removed.