0.3.6

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

Upgrading from 0.3.5 needs nothing from you. Your first sync after updating copies nothing, because each device checks the sync folder once more. The second sync carries on as usual; it comes one sync interval later, or run Sync now again at least 90 seconds after the first.

What changes

• Busy sync folders no longer starve. Before, every sync spent its files-per-sync limit on sessions that had not changed. Some sessions then waited days to sync. Now only files that actually have to be read count against the limit. A session turned away five syncs in a row gets through on a separate allowance, longest-waiting first, and the sync report says so when that queue is backing up. With two machines, an unchanged session is no longer read again on every sync: each machine remembers what it last read from the sync folder.
• A conversation Codex has compressed stays compressed. Codex can compress a session left untouched for a week into <name>.jsonl.zst. 0.3.5 did not recognise these files: it copied the sync folder's version back beside the compressed one, and Codex then read that copy. This version leaves a compressed conversation alone (compressed-here in the report). The one exception is when the sync folder's version is exactly what was compressed plus turns another device added; then it lands next to the compressed file. When the plugin cannot tell, it names the conversation instead. Open it in Codex once and quit without sending, let the next sync run, then continue. Pairs that 0.3.5 already created keep syncing normally. To tidy one up, delete only the .jsonl.zst, never the plain file: Codex would go back to reading the older compressed copy.
• An archived Codex conversation stays archived (Claudian 2.3.11 and later). The plugin no longer copies the sync folder's version back into the active folder on the device that archived it (archived-here). Your other devices keep syncing their copy.
• With the Claudian records provider on, a conversation you delete stays deleted on that device. This holds even when another device pushes it again, or when you point the plugin at a new sync folder. The report lists it as deleted-here. The new command Bring back conversations deleted on this device undoes it. Deletions are still never passed on to your other devices.
• Claudian 2.3.8 shrinking its records no longer pauses syncing. The plugin's "has the sync folder been emptied?" check no longer counts the bytes of conversation records.
• A warning before you send too early. If Claudian lists a Claude conversation here whose history is in the sync folder but has not reached this machine yet, the sync report names it. A pop-up also names it on the first sync after Obsidian starts. Wait for the sync that brings the history: sending first makes Claudian remove or reset the conversation.
• New command: Audit the sync folder (read-only). It shows what the sync folder still holds, such as conversations kept off this device and sessions no record in this vault names. It changes nothing and has no delete button.

These were tested on two Macs (Claudian 2.3.20, Codex CLI 0.158 and 0.160, Dropbox). The release main.js is byte-identical to the build that was tested.

Known issues, fixed in the next release

• A new device, or a vault whose .claudian folder is missing. The plugin restores the conversation records into the folder, as intended. But that sync's report still says the Claudian provider is "unavailable", and the "conversation folder was recreated" note appears one sync later.
• After Claudian's conversation folder is recreated (rare): a record whose restore failed or was interrupted in that sync can be listed as deleted-here afterwards. Bring back conversations deleted on this device restores it.
• Restore screen titles read "from the this machine".
• Opening a Codex conversation may add a line to it (seen once, not yet confirmed). If it does, following the "open it once and quit without sending" advice can end in a conflict when the other device has also continued the conversation. Both versions are kept, and nothing is lost.