Repository navigation
Session Preserve — durable, verifiable Codex session preservation, now multi-provider #45238
davidqyc
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Update: the project I originally posted here as codex-preserve has grown into Session Preserve v0.2.0.
The Codex use case is still the same: take an already-persisted local Codex session, create an independent readable preservation package outside Codex, and verify that package later.
It now uses one schema-3 package format across:
Repo: https://github.com/davidqyc/session-preserve
PyPI: https://pypi.org/project/session-preserve/
Install:
For Codex:
Schema 3.0 uses provider-neutral member names such as:
so the localization question in my original post is now resolved.
The integrity claim remains deliberately narrow: verification checks the files attested by the package manifest against their recorded sizes and SHA-256 values. It does not prove authenticity or authorship, and a coordinated rewrite of both a payload and its manifest can still verify.
It is also still not
codex archive, not a restore/import tool, and not a sync service. Source sessions are read-only.The old
codex-preserve 0.1.3release remains available, and Session Preserve continues to verify legacy schema 2.1 / 2.2 packages.This is an independent, unofficial project and is not affiliated with or endorsed by OpenAI.
All reactions