True thin-client / lazy sync
Big fan, heavy user here. I need a way to keep my full history in the cloud while only loading what I open locally.
Current pain
After a wipe, local IndexedDB quickly grows back to ~500–650 MB and the app gets sluggish/freezy.
Some image-heavy threads are excluded by the per-chat size cap.
Full exports sometimes crash (“Aw, Snap!”).
What I’ve tried
Wiped local cache (IndexedDB) via DevTools; in-app “Delete all local data” has crashed before.
Optimize rendering ON, 25 msgs/page, auto-archive ON, auto-delete OFF.
Split mega threads, trimmed attachments, exported in smaller batches.
Ask
A lazy/partial sync mode: don’t rehydrate everything; fetch folders/chats on open, attachments on demand.
Option for cloud-only archive (visible/searchable, not loaded until opened).
Guidance on the best setup today to keep local tiny without losing history (e.g., text-only sync for older chats?).
Cloud Sync is great for backup, but it rehydrates too much locally—so it isn’t solving performance for big libraries. I’d gladly pay for a plan that delivers true thin-client behavior. (Also, would love to hear any recommendations to deal with this issue)
Log in to comment and vote
Comments2
Aug 19, 2025
PinnedThe latest update should eliminate the “chat too big” issue and also address all the lag/sluggishness/performance issues.
Can you try reload the app to see if it improves now?
https://feedback.typingmind.com/changelog/performance-update-2
Black Stream
Aug 19, 2025
Amazing — it feels like a huge improvement! (Though I should mention I had previously deleted all my file data and re-synced from the cloud without files, which helped quite a bit as well.)
Thank you so much!