What
Currently Zen Sync can READ local state, encrypt it, push to relay, pull from relay, and decrypt. But it doesn't write the decrypted remote state back to the local Zen profile.
Why
Without the WRITE path, the extension can only backup/poll state but can't actually sync (restore remote state on a new device).
How
The native host needs to:
- Take decrypted remote state (spaces, tabs, groups, folders, containers)
- Write it to zen-sessions.jsonlz4 (with proper mozlz4 compression)
- Signal Zen Browser to reload (or require restart)
Challenges
- Writing to zen-sessions.jsonlz4 while the browser is running may conflict
- Zen restores from session store on startup — may need browser restart
- Need to handle workspace UUID collisions (same UUID on different devices = merge, not overwrite)
Labels: write-path, enhancement, help wanted
What
Currently Zen Sync can READ local state, encrypt it, push to relay, pull from relay, and decrypt. But it doesn't write the decrypted remote state back to the local Zen profile.
Why
Without the WRITE path, the extension can only backup/poll state but can't actually sync (restore remote state on a new device).
How
The native host needs to:
Challenges
Labels: write-path, enhancement, help wanted