0.2.0

Install or update via BRAT: powoct/claudian-session-sync. See the README for setup.

Upgrading from 0.1.0 needs nothing from you — your sync folder, workspace identity and provider settings carry over, and every provider stays exactly as you had it.

Grok

Grok is supported now, and off by default like every provider.

A Grok session is not a file, it is a folder, and its files do not agree about how they are written: the conversation history is appended to, while the record that makes the session visible to the CLI is rewritten whole every time Grok starts. So they travel under different rules — the history merges by prefix, the record only ever fast-forwards from a version this machine has seen both sides agree on, and anything ambiguous becomes a conflict you decide rather than a guess.

What travels is the conversation and its history. The files Grok rebuilds by itself — its prompt context, its system prompt, its event log — are deliberately left where they are, partly because copying them buys nothing and partly because one of them holds this machine's paths. Seeing more files on the other machine than were synced is expected, not a bug.

Measured on macOS and Windows before shipping, and verified end to end across two machines in both directions: start a conversation on one, resume it on the other with its full history, continue, and come back.

Claudian conversation records (optional, off by default)

Carries the entries in Claudian's own sidebar — titles, and which CLI session belongs to which conversation — for setups whose vault sync cannot carry .claudian/. Obsidian Sync drops hidden folders; git and Syncthing usually do not.

Leave this off if your vault sync already carries .claudian/. Two transports over one folder is how a sync tool is handed conflicts to manufacture copies from.

Getting a version back

Every overwrite has always kept the version it replaced. Until now that promise lived on disk and nowhere else — you could only reach it by digging through folders. There is now a screen that lists what was kept, and each row says what restoring it will actually lead to before you press anything: nothing, a revert the next sync will undo, or a conflict where both versions survive and you choose. Restoring is itself reversible.

Also: Show me the folder now opens the folder, and the two commands that write on your behalf — resolving a conflict, restoring a backup — take the same lock and re-check the sync folder at the moment you click, rather than trusting what the last sync pass concluded.

Turning a provider on now shows you the scope first

Enabling a provider decides which of this machine's existing conversations start travelling, and that set is usually larger than the one you have in mind — it is every conversation this vault has a Claudian record for, not just today's. The first time you switch one on, a dry run happens immediately, writes nothing at all, and tells you to open Show last sync report before anything is copied.

Notes

• Where backups live changed. They now sit under a per-session subfolder, because Grok is the first provider whose file names repeat across sessions and a flat folder could no longer say which session a backup came from. Backups written by 0.1.0 stay listed and restorable where they are.
• A conflict can appear with only one machine involved. If a sync pass copies a session while the CLI is still writing it, the finished version may not be a continuation of what was copied. Nothing is lost — both versions are kept and you pick one — but it is worth knowing that it does not always mean two machines edited the same conversation.
• Grok's rewind and /compact have not been measured yet. If either rewrites history in place, it shows up as a conflict with both versions kept, never as lost bytes.

Full technical record, including what was measured and what was not, is in docs/zh-CN/ (Chinese).