Sync, restore, and sharing

Daily flow

unlose watch --install
unlose status
unlose sync status
unlose sync pull

The scheduled job captures locally first. When a sync account is connected, it encrypts and pushes changes. If no sync account is connected, the local capture succeeds without network access. A failed upload leaves the local capsule in place, and the next scheduled run retries it. Routine pushes advance a session only after the client proves the remote transcript is an exact byte-prefix of the local one. A real divergence stops for explicit review.

Restore or continue

unlose restore <session-id>
unlose continue <session-id>

restore performs exact same-ID recovery. continue restores missing state and hands the session to the creating agent.

Share a session

unlose share <session-id>
npx unlose open '<complete share link>'

The fragment after # is the share key and never reaches the server. Treat the complete link as a secret. Revoke an unclaimed link with unlose unshare <share-id>.