Session Preserve — Development skill for Claude Code
Local-first preservation and integrity verification for persisted coding-agent sessions from Codex, Claude Code, Kimi Code, and ZCode.
How to install Session Preserve
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open davidqyc/session-preserve and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Session Preserve does
Local-first preservation and integrity verification for persisted coding-agent sessions from Codex, Claude Code, Kimi Code, and ZCode.
Alternatives in Development
- Alethe Agents — A local-first desktop workspace for running, organizing, and resuming multiple coding agents and shells with r 511 ★
- Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★
- Lacp — Local-first policy, evidence, memory, and recovery controls for Claude, Codex, Hermes, and other CLI coding ag 300 ★
README
Session Preserve
**English** | [简体中文](README.zh-CN.md)
Session Preserve keeps an independent, readable copy of coding-agent sessions that are already persisted on your machine.
v0.2.0 supports four local sources: OpenAI Codex, Claude Code, Kimi Code, and ZCode.
The exported package records where its readable content came from, what the adapter could and could not establish, and a manifest of the package files. Later, session-preserve verify can check whether those manifest-attested files are still present and byte-identical to their recorded SHA-256 and size.
Source sessions are read-only. Session Preserve does not restore, resume, import, sync, reindex, repair, archive, or delete them.
If you only need a readable transcript, use the product's built-in export surface when one is available. Session Preserve is for keeping an **independent preservation package** with provenance, coverage information, and later manifest-relative integrity verification.
Install
python -m pip install session-preserve
Python 3.9 or newer. The runtime has no third-party Python dependencies.
session-preserve --help
session-preserve --version
Project pages: [GitHub](https://github.com/davidqyc/session-preserve) · [Releases](https://github.com/davidqyc/session-preserve/releases) · [Issues](https://github.com/davidqyc/session-preserve/issues)
Quick start
Every new export uses package schema 3.0.
Codex
List sanitized candidates:
session-preserve export codex --list-candidates
Export one exact persisted session:
session-preserve export codex --session-id --output-dir ./exports
You can also select an exact rollout file with --rollout.
Claude Code
Select one top-level session JSONL explicitly:
session-preserve export claude --source ~/.claude/projects/.../.jsonl --output-dir ./exports
The default Claude Code store is under ~/.claude/projects, or $CLAUDE_CONFIG_DIR/projects when conf
Related Skills
Agent Pigeon
See how your coding agent actually worked. A tiny local CLI that turns Claude Code / Codex sessions into fligh
Shared Agents IDE
Local-first desktop app where a team shares coding-agent sessions and memory. Watch a teammate's Claude Code o
Solenta
Solenta - local-first desktop control surface for coding agents (Claude Code, Codex, Kimi, Grok, OpenCode)
Agent Memory Layer
Local-first shared memory + skill governance for multiple coding agents (Claude Code / Kimi Code / DeepSeek Ha
Recallnest
One memory, every terminal. Shared memory layer for any MCP client — Claude Code, Codex, Kimi, Antigravity (ag
Nebulous
NewsBlur MCP server and Web Capture Archive Protocol orchestrator — local-first feed/story index, plus URL pre
Related Agents
Kimi Worker
Forward a coding, diagnosis, or review task to Kimi K3 (Moonshot) through the local kimi-worker.sh runtime. Us
Ade
Agent sessions routinely outlast the machine that started them, and checking a Claude Code or Codex run from a
Kimi K3 Worker
Coding worker on Kimi K3, served by the multi-model gateway's upstream. Use when the user says "use kimi", "ki