Messaging

DMs that stay between you

One inbox for every conversation, encrypted by default and identical on all five clients — including the terminal.

End-to-end encrypted session keys on device
NANadiatyping…
KWKwame2 unread
INInesread

Can you check the node logs? The webhook retried twice.

Looking now — it was a clock skew on our side, fixed in 1.0.1.

delivered to 3 devices
👍 3🔧 1

Encrypted DM thread, synced across a phone, a desktop and the CLI.

What you get

Built for the way you actually work

Every client speaks the same protocol, so nothing here is a mobile-only or desktop-only promise.

End-to-end encryption, on by default

Keys are generated on your device and never leave it. The node stores ciphertext plus the routing metadata it needs to deliver — nothing else.

Threads, reactions and full-text search

Reply inside a message instead of flooding the channel, react to keep the thread short, and search locally over the history you already have.

One inbox across five clients

Read on Android, answer from the CLI, finish on Windows. Read receipts, typing state and drafts share the same store.

Message like it is private

Install a client and your first encrypted DM takes about a minute — no account approval needed.