v0.7.9

Session Cartographer 0.7.9

This release brings Codex's own memory into /remember, sharpens /standup,
and rebuilds /investigate around recall. It includes everything from 0.7.8,
so if you are upgrading from 0.7.7, these notes cover both.

Codex memory in recall

• /remember can now search what Codex has saved in its native memory, next to
  your Claude Code and Codex session history. Import it once, and again whenever
  Codex's memory changes:

  node plugins/session-cartographer/scripts/backfill-codex-memories.js

  Add --dry-run to preview, or --index to include the entries in semantic
  search when Qdrant and the embedding server are running. The import never
  writes to Codex's files.

• When a Codex memory entry changes or is removed, recall shows only the current
  version. Earlier versions stay in the log as history.

• Current Codex preferences feed the standing profile (.carto/profile.md).

• See the Codex memory migration guide if you are
  upgrading an existing install.

/investigate remembers past diagnoses

• Before you diagnose a bug, /investigate now searches earlier investigations
  of similar symptoms and files, and shows whether each was confirmed or
  refuted. A hypothesis that was already ruled out is the most useful thing it
  can surface.
• It records your hypothesis, and once the fix is verified, the outcome, so the
  next session starts from what was learned.
• It no longer imposes a debugging procedure; how to debug is left to you and
  your agent.

/standup

• Edits to the same file from a Codex worktree and its main checkout now count
  as a collision, as Claude Code worktrees already did.
• --project matches files by the repository they belong to, not by any folder
  that happens to share the project's name.
• --commit respects --since.
• Session labels stay distinct when two session ids share a prefix.

Project registry

• The plugin now ships without project aliases. Build yours from your own
  history, and refresh it later without losing your edits:

  node plugins/session-cartographer/scripts/bootstrap-project-registry.js --dry-run
  node plugins/session-cartographer/scripts/bootstrap-project-registry.js
  node plugins/session-cartographer/scripts/bootstrap-project-registry.js --update --dry-run

  --project substring matching works without a registry, so most scoped
  searches need no setup.

Turbo

• The README now leads with measured recall speed: about 0.3 s with Turbo
  against about 12 s without, on a 150,000-event corpus. Reproduce it on your own
  history with bash plugins/session-cartographer/scripts/bench-grep-vs-turbo.sh.
• Turbo no longer leaves a stray background server behind when its state
  directory is reset.

Upgrading

Update the plugin in every agent you use, then start a new session:

claude plugin update session-cartographer@session-cartographer --scope user
codex plugin add session-cartographer@session-cartographer

Update Claude Code and Codex together if you use Turbo. They share one
background server, and the first recall after an update replaces a server from
a different version, so two versions would keep replacing each other. Codex may
ask you to review changed hooks in /hooks. Paths above are relative to the
extracted release archive or a source checkout.