0.3.3

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

Upgrading from 0.3.2 needs nothing from you.

If you use Codex and have ever rewound a conversation, some of it was not syncing

Codex changed how it names a conversation's file. When you rewind — undo back to an earlier point — it does not rewrite the file. It writes a new one, leaves the old one exactly where it was, and remembers internally which is current. The new file is named slightly differently, and this plugin did not recognise the new shape.

The consequence was the bad kind of quiet. The rewound conversation's newest history never left the machine, while the older file kept syncing normally and the plugin reported up to date every time. Nothing looked wrong from here; the other machine simply had less than you did.

Both files now travel, which is what Codex expects — it keeps the old ones on purpose.

Nothing you already have changes. For a conversation you have never rewound, the naming is what it always was, and this release moves nothing on disk.

And the part meant to stop this happening again

That was the third time something upstream changed shape and this plugin went silent about it rather than wrong: Claudian moved its records into a new folder, this plugin published records when you only meant to look, and now Codex renamed a file. Each time the plugin did not make a mistake — it said nothing, which is harder to notice and took longer to find.

So Codex's sessions folder is now counted, not just read. Any file there this version cannot make sense of is reported by name, in Show last sync report under Notices:

Codex's sessions folder has 1 file(s) this version does not recognise and will not sync (…). If Codex has been updated, this plugin probably needs to catch up — the conversations in them are not travelling.

It deliberately does not try to work out why a file is unfamiliar, which is what lets it fire for shapes nobody has seen yet — including the compressed .jsonl.zst files Codex is preparing but has not switched on. Normally that notice is absent, and files your sync tool or this plugin created are not counted, so it stays worth reading.

If you see it today, the file it names is one whose conversation is not reaching your other machines — that is worth knowing either way.

Notes

• A sync pass could be brought down by a single long file name. The failed backup was meant to cancel just that one file's update; instead it stopped the whole pass, for every CLI. It now cancels only what it was protecting, and says which error it hit.
• Codex conversations started outside Claudian are still not synced, and that has not changed — this plugin syncs the conversations your vault has a Claudian record for. Worth stating because a rewound conversation started from a bare terminal will not appear no matter what this release fixes.
• Not measured yet: whether Codex's compression, once enabled, needs more than the warning above; and the two-machine case for rewound conversations — this round was verified on one machine.

For the record

The build published here is byte-for-byte the build that was acceptance-tested (f891de1b…), and you can check its provenance:

gh attestation verify main.js --owner powoct

Full technical record — including the four corrections the acceptance run made to its own script, and the one observation that looked like a defect and was not — is in docs/zh-CN/ (Chinese).