Sync Threadwell
Between Computers

For a normal Store installation, install the same Chrome Web Store listing on both computers. Chrome provides the matching extension identity. You do not need to copy a public key or manually set an extension ID.

Unpacked development builds are different: two folders can load as different extension identities, which cannot share Chrome Sync data. Developers should follow their package’s installation instructions and confirm matching IDs and versions before setup. Moving from an older development build needs care to preserve local data; contact support before changing installations.

If no synced collection exists yet, the first computer publishes its organization. If one already exists, the joining computer keeps the existing synced values for matching items instead of overwriting them with an old local arrangement. Local-only items and additional metadata can be added. An item already deleted in sync is not automatically restored by an old local copy.

This is first-join behavior, not a permanent preference for Computer 1. Once joined, edits on either computer synchronize in both directions. Turning sync off and on again does not necessarily make a previously joined computer a new joiner.

A successful save on Computer 1 does not prove delivery to Computer 2. Wait and inspect Computer 2 before editing. If neither computer has the arrangement you expect, stop and use recovery.

1. On each computer, open Settings and backup → Set up device sync. Uncheck Sync my organization between computers and click Save sync setting. Verify Sync is off on both. Unchecking without saving is not enough.
2. Update both computers to 0.4.26 using the appropriate Store or development update method. Verify the version on each and keep sync off.
3. Retain both exported backups. Do not rearrange items while recovering.

1. In Set up device sync, choose Optimize sync storage.
2. Read the dialog. Check Both computers are updated to Threadwell 0.4.26, and device sync is off on both. only when true. Click Optimize storage.
3. Wait for Sync storage optimized. If an error appears, stop and save a diagnostic; do not enable sync to bypass it.

This saves a local safety backup, checks stored snapshots, and removes obsolete sync copies owned by Computer 2. Its current cloud copy, other computers’ copies, and local folders are kept. Sync stays off. It does not remove your chats or guarantee that every large collection will fit.

1. Keep sync off. Wait for Chrome to deliver the cleanup. Use Save sync diagnostic on Computer 1 and have support confirm that the optimized storage is visible there before continuing. Computer 2’s success message alone does not confirm remote delivery.
2. Check Computer 1’s folders again. Choose Use this computer’s arrangement.
3. Read the dialog and check both confirmations: Both computers are updated to Threadwell 0.4.26, and device sync is off on both. and This computer has the arrangement I want to use for shared items.
4. Click Use this arrangement. Wait for This computer’s arrangement saved. If a limit or another error appears, stop and contact support.

Threadwell saves a local safety backup first, checks the current cloud snapshots, and publishes Computer 1’s choices for matching items: names, placement, order, colors, tags, Favorites, saved views, and templates. Missing shared fields use Computer 1’s defaults. Items found only on another computer are retained. Items currently present on Computer 1 can be restored even if they were previously deleted in sync.

This is a one-time recovery choice. It does not make Computer 1 the permanent master, and it does not turn sync on.

1. Computer 2: keep sync off while waiting for the saved arrangement to arrive through Chrome. Save a new sync diagnostic and have support review delivery before enabling sync. The report checks stored data; it does not preview folder names.
2. Computer 2: check Sync my organization between computers and click Save sync setting. Use Sync now if needed.
3. Computer 2: inspect folders, nested placements, colors, and saved chats. Confirm Computer 1’s arrangement and the items found only on Computer 2 are present.
4. Computer 1: only after Computer 2 looks correct, check Sync my organization between computers and click Save sync setting.
5. Run the empty-folder test in both directions.

Later edits synchronize both ways. Incoming arrangement changes save a local recovery point before they are applied. Find safety snapshots in Settings and backup → Schedule and restore backups; retain separate exported backups too. Local history has retention and storage limits and is not an unlimited archive.

• Sync is off: this computer is not exchanging organization automatically. Existing cloud data is retained.
• Ready to sync / Syncing / Waiting for Chrome Sync: check Chrome Sync and your internet connection, allow time, then try Sync now when enabled.
• Sync enabled: the attempt succeeded locally. “Saved to Chrome Sync. Other computers update when Chrome sync is available.” does not confirm that the other computer has received it. Last sync records this computer’s successful attempt.
• Sync storage optimized / This computer’s arrangement saved: the recovery action succeeded locally; sync remains off. Confirm delivery separately.
• ChatGPT account does not match: stop and check the ChatGPT account and workspace on both computers.
• Confirm ChatGPT workspace: only if both really use the same workspace, check I confirm these collections are from the same ChatGPT workspace. and choose Confirm and sync. Matching user IDs and saved items alone do not authorize joining different workspaces.
• Sync size limit reached / Sync needs attention / Sync is unavailable: read the accompanying message, keep backups, and save a diagnostic if it persists.

Chrome Sync has a small allowance. Threadwell uses a 96 KiB safety limit within Chrome’s 100 KiB quota for this extension. The display rounds sizes to KB. Usage includes retained copies and other sync data for this extension; temporary space is needed to publish safely. Large collections or several devices can still reach the limit even in 0.4.26.

A storage error keeps the local collection and last committed cloud snapshot safe. Use the separate recovery path with support. Optimization reclaims obsolete copies from the computer running it, not every computer. If the collection still cannot fit, exported backups can be transferred with Import backup; that is a manual transfer, not ongoing sync.

Use Settings and backup → Set up device sync → Save sync diagnostic when a storage, workspace, validation, or delivery problem persists, and at the recovery checkpoints above. Save one from each computer and label them Computer 1 and Computer 2. Share them with Support, together with the version and visible status message.

Diagnostics are read-only reports, not backups. They contain storage measurements, counts, formats, validation results, and account-marker match checks. They exclude chat titles, URLs, message bodies, account identifiers, credentials, and snapshot contents. Nothing is sent automatically. A diagnostic cannot restore your organization.