Feature Request: Cross-Device Sync for History, Commands, and Settings

[AnRkey]

1. The Problem (My User Story)
As someone who uses Witsy on multiple devices (in my case, three separate computers), my experience is currently disconnected. My conversation history, custom AI commands, scratchpad contents, and application settings are unique to each installation. This fragmentation means I cannot seamlessly switch between my machines and have to manually duplicate my setup, which is inefficient.

2. Proposed Solution
I propose the implementation of a sync feature. I believe this could be approached in two ways:

Primary Method: Sync via User-Managed Cloud Storage Allow users to define a specific directory for Witsy's data files. Users could then point this to a local folder that is synced by a third-party service like iCloud Drive, Google Drive, OneDrive, or Dropbox. This method is secure (as it relies on the user's own trusted cloud provider) and gives the user full control over their data.

Optional Premium Feature: Dedicated Sync Service As a future enhancement, a built-in, first-party sync service could be offered. This would provide a more seamless, zero-configuration experience for users. This could also be a great way to support the project financially by offering it as an optional paid feature.

3. What Should Be Synced?
To solve the problem, the following data should be included in the sync:

High Priority:

• Conversation History
• Custom AI Commands
• Scratchpad Content
• Application Settings (e.g., theme, default models, etc.)

Nice-to-Have (with security in mind):

• API Keys

Security Notes: Syncing API keys would be very convenient. However, this should be handled with extreme care. Perhaps it could be an opt-in feature with a strong security warning, or keys could remain device-specific to ensure maximum security.
Implementing this would transform Witsy into a truly portable and powerful tool for users who work in multiple environments.

Thanks for developing a brilliant application and taking the time to consider my idea.

[nbonamy]

Yep. Would love to have that too for me :)

In fact, started to work on it but dropped them

• 2a86cb4
• 6995b2f

Besides the main challenge of synchronization (merge conflicts when one or two devices are offline...), handling edge case scenarios is not trivial: history chats can depend on a document repository being available but document repositories can be quite large so syncing them is probably out of the question.

One easier way to address this would be allow to define a location for the Witsy settings and data. You could define this in your Dropbox or Google Drive local folder and synchronization will be handled by Dropbox/Google. Not sure how conflict would be resolved too...

[AnRkey]

I have noted other open source problems have had similar sync issues when using shared drive services. What about possibly supporting an SQL backend?

…

On Mon, 4 Aug 2025 at 18:12, Nicolas Bonamy ***@***.***> wrote: Yep. Would love to have that too for me :) In fact, started to work on it but dropped them - 2a86cb4 <2a86cb4> - 6995b2f <6995b2f> Besides the main challenge of synchronization (merge conflicts when one or two devices are offline...), handling edge case scenarios is not trivial: history chats can depend on a document repository being available but document repositories can be quite large so syncing them is probably out of the question. One easier way to address this would be allow to define a location for the Witsy settings and data. You could define this in your Dropbox or Google Drive local folder and synchronization will be handled by Dropbox/Google. Not sure how conflict would be resolved too... — Reply to this email directly, view it on GitHub <#370 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASCJVRIZCQS4RAPCURXQ3ZL3L6A55AVCNFSM6AAAAACDAN523WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJZGEZDANA> . You are receiving this because you authored the thread.Message ID: ***@***.***>