Codex SyncKit 0.2.0-alpha
Pre-releaseCodex SyncKit 0.2.0-alpha
This release makes cross-device Codex automation handoff safe for the intended
workflow: use Managed ChatGPT on one Windows PC at a time, close it, wait for
OneDrive, and continue on another PC.
Highlights
- No duplicate scheduled runs after switching PCs. Managed Pull imports
completed shared run records into the current device's local scheduler and
advances only an olderlast_run_atwatermark. The next due time is then
recomputed by ChatGPT. - No mass unread state from imported history. Completed runs imported from
another device are recorded asARCHIVED. - Local databases stay local. Neither
state_5.sqlitenor
.codex\sqlite\codex*.dbis copied or linked through OneDrive. Only portable
definitions, memory, rollouts, and completion watermarks cross devices. - Managed launch fails closed. Missing scheduler schemas, current shared
definitions, incomplete run coverage, or a changed database hash stop launch
instead of allowing an automation to appear asLast run: never. - Retired definitions do not block startup. Historical runs for deleted or
replaced automation IDs remain visible as history but are not treated as a
missing current definition.
The release also includes the local Memory Observatory, safer synchronized
project-workspace conflict handling, portable projectless workspace paths, and
the accumulated improvements listed in the changelog.
Upgrade
- Close Managed ChatGPT on every PC and let OneDrive finish synchronizing.
- Download and extract
codex-synckit-0.2.0-alpha.zip. - Run
Install-CodexSyncKit.cmdon each PC that uses the shared Kit. - Open and close ChatGPT once on every PC before enabling automation sync, so
its local scheduler database and tables exist. - Continue launching only through the managed
ChatGPTshortcut, on one PC at
a time.
Existing installations are repaired in place and retain rollback backups. Do
not manually copy either Codex SQLite database between devices.
Verification
The automation handoff and launch checks were exercised on three independent
Windows devices. The release pipeline also runs the public-source gate, builds
and re-extracts the ZIP, rescans the extracted artifact, and executes the Node,
PowerShell, and memory-subsystem regression suites before publishing assets.
This remains an alpha release focused on Windows and OneDrive. Keep the shared
CodexKit directory private and maintain an independent backup of important
work.