0.3.0

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

Upgrading from 0.2.0 needs nothing from you. One setting changes on its own, and it is described at the bottom.

If you are on Claudian 2.2.5, 0.2.0 stopped syncing new conversations — silently

This is the reason to update. From 2.2.5 Claudian files each new conversation's record under the device that made it, in a folder that did not exist before. This plugin looked in one place, did not find the record, and concluded the conversation was not one of this vault's. So it synced nothing — no line in the report, no notice, and the status bar saying up to date the whole time, because from the plugin's point of view there was genuinely nothing to do.

Conversations from before 2.2.5 were unaffected, which is what made it hard to notice: everything old kept working.

Fixed, and verified on two machines rather than only in tests — a bug whose symptom is nothing happening is exactly the kind that passes a test suite.

The same failure will not be silent next time

The plugin now says which folders inside Claudian's conversation store it did not read. Normally that list is empty and you will never see the notice. If Claudian moves its records again, it appears in Show last sync report under Notices, naming the folder:

Claudian's conversation store has folders this version does not read (…). Conversations recorded in them are not synced. If Claudian has been updated, this plugin probably needs to catch up.

That is the whole point of this one. The cost of the bug above was not the bug, it was the weeks it could have run without a word.

A conversation you rewound is no longer quietly put back

Grok's rewind was measured, on a real machine, at byte level: it truncates the history file in place. The version left behind is a strict prefix of the one still sitting in the sync folder — which reads exactly like "this machine is behind", and 0.2.0 acted on that reading and pulled the longer version back. The rewind was undone, without a word, and the same pass pushed the post-rewind state of a neighbouring file out, leaving a mix neither machine had ever had.

Now a file that has shrunk below a point both sides once agreed on is a conflict: both versions are kept, nothing is overwritten, and you choose. The rest of the session's files stop travelling until you do, so no half-state gets published on your behalf.

The window was only ever open between a rewind and your next message. That sounds narrow, and it is — unless you rewound in order to drop something and then closed the terminal, which is the use that matters most.

/compact rewrites the file wholesale rather than truncating it, so it already landed on the safe branch. Both are measured and written down.

New: share this device's conversations with your other devices

Off by default, and set per machine — turning it on here does not turn it on there.

On 2.2.5, a conversation you start on one machine is missing from the other machine's sidebar even after its session file has arrived. Resuming from the CLI works; the entry in the list is what is absent, because Claudian reads only its own device's folder.

This setting moves each of this machine's conversation records into the layer every device reads. All of them then list it, and all of them write to the same one — rename it on the laptop and the desktop shows the new name.

Three things to know before you turn it on, all of them in the setting's own description:

• It moves the record rather than copying it. There is one of it, so there is no second version to drift. (An earlier design copied; it was withdrawn before shipping, because two writable copies of one conversation never converge and a deleted conversation would come back.)
• Turning it back off stops further moves but does not un-share what has already been shared. Moving records back would be a second destructive write, on records the other machine may be using.
• A shared conversation carries any folders it had been given access to, as absolute paths. On the other machine those paths may point at something else. This is not new exposure — it is exactly what every conversation looked like before 2.2.5 — but it is worth knowing.

The button labelled Assign to this device that appears on a shared conversation does the opposite of this setting: it takes the record for one machine and makes it vanish from the others. It sits next to the delete icon.

The quiet window is 15 seconds now, and this one may change under you

A file is only written when both sides have held still for a while. That wait was 3 seconds, which was a guess. It has been measured: sampling a single Grok turn at 100 ms, the session held entirely still for 3.3 seconds mid-turn — long enough for the old default to conclude a turn had finished when it had not. The new default is 15 seconds.

If you had never changed this setting, it moves to 15 seconds on upgrade. If you had set your own value, it is kept — with one honest exception: if your value was exactly 3000, we cannot tell you from someone who never touched it, so it moves too. Set it again if you meant it. Passes are five minutes apart; the extra twelve seconds are not something you will feel.

Notes

• A half-copied session can now be cleared. If a sync pass is interrupted partway through a multi-file session, the leftovers are listed and removable — and never removed without you asking.
• Which vault this machine is bound to is now decided by the vault that is actually open, not by whichever one sorted first. This only ever mattered if you opened this plugin in more than one vault.
• Not measured yet, and written down as such: Codex did not take part in this round's two-machine run; carrying one conversation record over both your vault sync and this plugin at the same time; and two machines creating, editing and deleting the same record at the same moment.

Full technical record — including what was measured, what was assumed, and the three deviations the acceptance operator logged rather than smoothed over — is in docs/zh-CN/ (Chinese).