Offline Mode

No WiFi. Still protected. DevSafe queues encrypted backups locally when you are offline and ships them automatically when your connection returns.

What it does

When DevSafe detects no network connectivity, it continues creating encrypted backups and stores them in a local queue. Nothing changes about how your backups are created or encrypted. The only difference is where they wait.

When connectivity returns, queued backups upload automatically in the order they were created. There is no gap in coverage. Every backup that would have gone to the cloud is preserved locally until it can be delivered.

Usage

Offline Mode is automatic. There is no special command to enable it. DevSafe detects connectivity on its own and switches between local queuing and cloud upload transparently.

Two commands are useful when you are offline:

Check queue status

Use devsafe status to see how many backups are queued locally and waiting for upload.

$ devsafe status
Status:        offline
Queued:        3 backups pending upload
Last backup:   2 minutes ago (local)
Repos tracked: 4

Force a local backup

Use devsafe backup --force to trigger an immediate local backup, even when offline. Useful before shutting your laptop down on a long flight.

$ devsafe backup --force
✓ backup created (queued locally, will upload when online)

When it matters

Offline Mode exists for the real-world moments when connectivity disappears but your work does not stop:

• Flights -- hours of focused coding with no internet. Every save is still backed up.
• Train rides -- spotty connections that drop mid-upload. DevSafe retries automatically when signal returns.
• Coffee shops with bad WiFi -- unreliable networks do not mean unreliable backups.
• Remote locations -- cabins, campsites, or anywhere cellular coverage is weak. Your backups queue silently and upload later.

In every case, your backup schedule continues uninterrupted. You do not need to remember to "sync" when you get back online. DevSafe handles it.

Storage

Queued backups use the same encryption as cloud-bound backups. A backup sitting in the local queue is encrypted with the same key, the same nonce-unique AEAD, and the same envelope format as one that uploads immediately. Queued backups are indistinguishable from cloud backups in every way except location.

Once a queued backup uploads successfully, it is removed from the local queue automatically. There is nothing to clean up manually.