Session Preserve v0.2.0

Session Preserve v0.2.0

This is the first multi-provider release under the Session Preserve name.

Supported local session sources

• OpenAI Codex
• Claude Code
• Kimi Code
• ZCode

New package format

New exports use package schema 3.0 with provider-neutral physical member names:

• conversation.md
• export.receipt.json
• package.manifest.json
• optional attachments/
• optional artifacts/ and artifacts/index.md

session-preserve pack can create a deterministic derived session-package.zip after the canonical package verifies.

Compatibility

The verifier continues to support legacy Codex package schemas 2.1 and 2.2. The previously published codex-preserve 0.1.3 release remains available and is not yanked.

Integrity and scope

Session Preserve verifies manifest-relative file integrity using recorded sizes and SHA-256 values. It does not claim authenticity, authorship, or that every message visible in an agent UI had already been persisted to disk.

Provider adapters retain their own source semantics; this release does not introduce a generic provider/plugin SDK or a cross-provider conversation ontology.

Install

python -m pip install session-preserve==0.2.0
session-preserve --help

PyPI: https://pypi.org/project/session-preserve/0.2.0/

codex-preserve 0.1.3

codex-preserve 0.1.3

Compatibility patch for current persisted Codex lifecycle records.

What changed

• Export core 2.2.0 → 2.2.1.
• Recognizes terminal McpToolCall records currently persisted by Codex.
• Recognizes turn_aborted and treats a valid abort as the terminal outcome when the same turn also has a completion record.
• A turn that is later aborted is therefore no longer counted as completed.
• Private MCP arguments, results and errors remain omitted from public export payloads.
• Unknown future schema remains fail-visible rather than guessed.

Compatibility

• Conversation package schema remains 2.2.
• Existing schema 2.1 / 2.2 packages remain verifiable.
• This release does not add restore, reindex or repair behavior.
• If all you need is a Markdown copy of the current TUI conversation, Codex CLI 0.148.0+ already includes /export; codex-preserve remains focused on durable packages, provenance and manifest-relative verification.

Validation

The tagged tree passed the release workflow build, public hygiene scan, full deterministic test suite and three-state examples before publication. PyPI publication used Trusted Publishing (OIDC).

v0.1.2

• Version-identity consistency repair: codex-preserve --version now reports the same version as the installed distribution (0.1.2). Previously the CLI banner lagged the published metadata.
• Added a regression test guarding distribution/package/CLI version identity on all supported Python versions (3.9+).
• No exporter or verifier behavior change; package schema (2.2) and export core (2.2.0) unchanged.

v0.1.1

v0.1.1 is a discovery/metadata patch release. No runtime behavior change.

• Corrected the public pip install/first-use path in the README (python -m pip install codex-preserve).
• Added four durable project URLs to the package metadata: Homepage, Repository, Issues, Release notes.
• Package distribution version: 0.1.1 (Apache-2.0).

Install:

python -m pip install codex-preserve

Note: the CLI --version banner reads the version string built into the export core (0.1.0); the published distribution for this release is 0.1.1, as reported by pip show codex-preserve.

v0.1.0

First public release of codex-preserve.

• Package: codex-preserve==0.1.0 on PyPI (wheel + sdist), published by the release.yml workflow via PyPI Trusted Publishing (OIDC).
• Source: tag v0.1.0 → commit cf4eb73e85a7b142f4166ed5bf8610118b865b9c (clean zero-parent public root, tree f184b6ae).
• CLI: codex-preserve console command with export and verify subcommands; conversation package schema 2.2.
• License: Apache-2.0.

Distributions are published on PyPI; this repository does not attach rebuilt artifacts.