Transparent Limitations & Storage Quotas

To build resilient software, developers need to understand what a library cannot do just as clearly as what it can.

---

What ContinueJS Protects Against

• ✅ Accidental tab closures.
• ✅ Browser crashes and OS restarts.
• ✅ Page refreshes and back-button navigation.
• ✅ Loss of Wi-Fi / network disconnects while typing.

---

What ContinueJS Cannot Protect Against

1. User Clearing Browser Site Data

If a user manually opens browser settings and clicks "Clear Browsing Data & Local Storage", the browser operating system wipes IndexedDB.

2. IndexedDB Quota Exceeded

Browsers assign per-origin storage quotas (typically up to 20% to 50% of available disk space). While ContinueJS drafts are extremely compact (a few kilobytes of JSON), if disk space is completely full, IndexedDB put() requests will fail. ContinueJS catches quota errors gracefully without breaking your app.

3. Malware or Malicious Extensions

If a user has installed a malicious browser extension with broad <all_urls> permissions, that extension can read DOM inputs or local storage within the browser environment. Client libraries running inside the browser DOM cannot defend against compromised browser extensions.

4. Cross-Device Synchronization

ContinueJS is strictly local-first. It does not synchronize drafts across a user's phone and desktop unless your backend API syncs local draft state to your database.