Pick up from
your last confirmed save.

Keep meaningful progress available beyond a single session. Supported terminal hooks save selected checkpoints and help the next session read them back.

memford / session-continuityIllustrated flow
  1. Session start

    Read the saved project context

  2. Selected checkpoint

    Save and verify the readback

  3. Next session

    Resume from confirmed knowledge

An abrupt exit cannot save work that was never confirmed remotely.

Capture useful progress, not every keystroke

After project consent, the terminal adapter lets an agent stage decisions, outcomes, open questions and next steps. Stop and PreCompact hooks upload staged changes and verify an exact readback. It does not capture full transcripts or run a periodic timer.

Verify the actual startup

The optional adapter supports local Codex and Claude Code command hooks on macOS and Linux with Node.js 22 or newer. Preserve existing instructions, review and enable the hooks, then prove that a fresh session received the saved context before a manual read. Installing a file is only one part of setup.

Recover from the last confirmed checkpoint

Startup loads current memory and retries a bounded part of the private local queue. Retry IDs prevent a lost response from creating duplicate notes. Pending changes still need their original computer and a working connection before other clients can read them.

The useful details

Recovery starts from the last confirmed remote checkpoint. It is not a guarantee against unsaved work lost during a crash. The optional adapter uses a separate project key in private local storage.

Give your next session a head start.

Copy one brief. Connect the project. Verify the first save.

Set up free