Session Save
Pick up where
you left off.
Session Save is a local session-memory system. It creates a handover record with the context, decisions, file references, open work, and next steps worth carrying into another session.
In a new Claude or Codex session, run Pickup, choose the project and saved session, review the cited handover, and confirm where to continue. Session Save never watches every chat or loads memory automatically.
One-time Terminal setup for both apps.
git clone https://github.com/youkistudios/session-save-system
cd session-save-system
./install.sh
v2.0.0-alpha.5 · requires Terminal + Python 3 · 41 automatic checks · installed on macOS · Linux testing is not finished
Not comfortable with Terminal? Ask a technical helper to do the one-time setup. Daily use is four deliberate workflow moments, plus Pickup when you need to resume. Session Save has no product cloud or background uploader, and it does not encrypt your notes. After disclosure and consent, Pickup sends only the selected notes to your active AI provider. Your folder may also sync through another service you configure.
Four capture moments, plus Pickup to resume.
Imagine Claude helps you plan a website today. Tomorrow, Codex helps build it. The saved handover gives you or the next AI a clear place to restart.
Illustrative local workflow · select a capture moment or Pickup
Give important work a clear name and project.
claude › /session-tag ✓ project selected: Website Launch ✓ source: Claude · state: LIVE → sessions/website-launch/claude/…/tag.md
In Codex, use $session-tag. Session Save asks which project this belongs to. It does not guess.
Save a short note before you stop or switch tasks.
claude › /session-checkpoint ✓ new checkpoint saved Now · Working on · Next · Watch → checkpoints/20260726-….md
In Codex, use $session-checkpoint. The older $session-save still works. In Claude Code, /ss still works. Each checkpoint is a new note; older ones stay unchanged.
When the work is done, save the result and restart notes.
claude › /session-close ✓ plain-English summary saved ✓ technical notes saved for later → human.md · agent.md
In Codex, use $session-close. The older $session-summary still works. In Claude Code, /ssum still works. Tag the work before closing it.
See recent saved notes from Claude and Codex in one place.
codex › $session-review [Claude] website research notes [Codex] website build summary → audits/global/2026-W30_audit.md
In Claude Code, use /session-review. The older /session-audit and /sa still work. In Codex, use $session-review or the older $session-audit.
Bring an exact saved handover into a fresh session.
claude › /session-pickup ✓ project selected: Website Launch ✓ saved session selected: Claude · exact record ✓ approved notes read after disclosure → cited brief · confirm one bounded next step
In Codex, use $session-pickup. Pickup lists metadata first, waits for consent before reading selected notes, and asks before acting. It is read-only resume access—not another capture moment.
This is a shortened example. Session Save prints the real local path after each save. Pickup reads only the exact bounded notes you approve and cites their real paths.
Use Pickup in a fresh session.
- Run Pickup
/session-pickupin Claude Code or$session-pickupin Codex. - Choose the handoverSelect the exact project and, when needed, the saved Claude or Codex session.
- Review, then continueApprove the listed notes, read the cited brief, and confirm one bounded next step.
Your memory is a folder you can open.
Session Save writes notes you can read in a normal text editor. Small organizing files tell it where each note belongs.
session-logs/ ├── _INDEX.md list made from saved notes ├── GUIDE.md shared instructions ├── sessions/ │ ├── _PROJECTS.md your project list │ └── session-save/ │ ├── claude/<date>_<slug>/ │ │ ├── record.json │ │ └── checkpoints/… │ └── codex/<date>_<slug>/… ├── events/ └── audits/global/
- One folder, both apps
- Claude and Codex keep separate notes inside the same project folder.
- You choose the project
- Session Save does not join projects because their names or topics look similar.
- Easy to inspect
- Open, copy, search, or back up the notes with normal file tools.
- A useful handover
- Save what happened, which files matter, what remains open, and what to do next.
What works now—and what is still being tested.
Claude and Codex notes stay separate, checkpoints leave old notes unchanged, projects require your exact choice, and Pickup returns only the selected bounded handover after consent. Install, crash recovery, migration, and uninstall are also tested.
The 41-check suite covers local writes, project safety, read-only Pickup, changed-note rejection, malicious-file boundaries, installer recovery, and record preservation. Important implementation claims have independent security review.
Real Claude-to-Codex and Codex-to-Claude Pickup journeys passed on macOS: exact project and session selection, refusal before reading, cross-client disclosure, cited briefs, a missing-workspace question, and confirmation before action. Both Session Save trees stayed byte-identical.
A second POSIX computer, Windows, more AI apps, and fresh Close/Review witnesses in both clients. These remain separate from automatic kernel proof.
Recording every chat, guessing which projects belong together, deciding project stages, changing your master plan, tracking you, or uploading notes to a Session Save cloud.
Seven clear answers.
What does Session Save remember?
It can remember what happened, what you decided, where the work stopped, which files matter, what remains open, and what should happen next. It saves file names and paths, but it does not copy every referenced file into the memory folder.
How do I pick up in another app?
Run /session-pickup in Claude Code or $session-pickup in Codex. Choose the exact project and saved session. Pickup shows which notes it would read, warns when they came from another AI client, and waits for consent. It then gives you a cited handover and asks before acting. This is user-confirmed resumption, not automatic continuation.
Does it record every chat?
No. You decide when to Tag, Checkpoint, or Close. Session Save does not secretly read old chats or run a background recorder.
Where are my notes kept?
The normal folder is ~/Desktop/session-logs/. You can choose another folder before installing. Session Save never moves an existing memory folder without asking.
Which command names should I use?
Use session-checkpoint, session-close, session-review, and session-pickup. Older save, summary, audit, and short names still work. If another Claude command already uses the same name, Session Save leaves it alone and keeps its skill available through the Skills menu.
Can it mix up two projects?
Session Save only joins notes when you choose the same saved project. Similar words or topics are not enough. Unknown project names stay separate for you to review.
Can I trust every saved summary?
Treat it like any AI-written note: check important details. Session Save keeps the note and its source, but it cannot guarantee that an AI summary is complete or correct.