All blog posts
Updates 2 min read

Commonveil 0.18.0: Offline mode

Commonveil 0.18.0 records offline mode. Here is the project history, technical detail and reasoning behind the update.

By Comutability Published Update from

Historical Commonveil release, 6 November 2026. Based on the project's official versioned release record. This does not establish an independent cryptographic audit.

Commonveil 0.18.0 records offline mode. Here is the project history, technical detail and reasoning behind the update.

Why this update matters

Private communication should be able to withstand an unreliable connection. The key principle is that a message is sealed on the user's own device when it is written, not saved as plaintext while waiting for the network. Offline mode and store-and-forward delivery are important for rural connections, local networks and independently hosted communities.

What changed in version 0.18.0

The official release notes recorded the following changes. These describe the version at the time, and later releases may have replaced, improved or removed particular mechanisms.

  • Keep writing with no connection: each message is encrypted and signed on your device straight away, waits there, and goes out when you're back, showing the time you wrote it.
  • Offline mode in settings stops the app reaching the server until you turn it off. Everything you send in the meantime waits, already encrypted.
  • If something changed while you were away, a waiting message is marked "Not sent", with Send again or Delete.
  • Self-hosted sites hold messages for other sites they can't reach, and pass them on when they can, for up to a week.
  • A self-hosted site can run on a small computer with its own Wi-Fi, so people nearby can chat with no internet. The guide is in docs/OFFLINE.md and docs/SELF_HOSTING.md.
  • New Help Centre articles: offline mode, people on other sites, sign-in and recovery, and running your own site.

How this fits the wider Commonveil direction

Comutability's wider aim is useful, accessible technology that gives people more control. For Commonveil that means encrypted communication, meaningful user permissions and the option to run a site independently. We also need to keep a clear boundary between what the project records as implemented, what has been tested and what still needs expert review.

The detailed release notes above provide a starting point for members and contributors to test the behaviour, read the documentation and challenge assumptions.

What to check next

Test interrupted deliveries, key changes while disconnected and the status shown when a queued message can no longer be sent safely.

Original sources

Sources and further reading

Explore the evidence and original project records behind this article.