Reinstate context and work across sessions. Return to a line of thought, recover why a decision was made, or bring an insight from another conversation into the task at hand.
Context accumulates through the work itself. Cartographer makes captured activity and retained conversations searchable, so you can recover the context a question calls for, whenever it arises. Follow an idea across sessions, revisit an earlier investigation, and connect work whose relationship only becomes apparent later. You can work organically without preparing a starting context for every future session.
Claude Code and Codex contribute to the same local history and can recall each
other's work; a read-only adapter brings Hermes history into the corpus too.
Use /remember to find the earlier reasoning and follow it back to its source
conversation, or browse the Explorer to reconnect with a thread of work.
Download a release · Setup guide · Changelog · Related projects
One day of recorded work: 31 tasks and 3,301 records across nine projects. Private project names are replaced for these screenshots.
Capture requires no LLM, and keyword recall needs no server. Semantic search and the Explorer are optional. The default setup keeps your history on your machine.
| Task | Skill | Result |
|---|---|---|
| Reinstate context | /remember <question> |
Earlier reasoning from across sessions, with links to the source conversations |
| Return to a project | /remember --project <name> |
Recent work, related projects, and recurring procedures to help pick up the thread |
| Explore a thread of work | /carto |
Search, timelines, and transcripts for moving between session contexts |
| Preserve what emerged | /wrapup |
Decisions, discoveries, and unfinished questions made easier to return to |
| Revisit an investigation | /investigate <bug> |
Earlier diagnoses brought into the current investigation, with hypotheses tracked through verification |
| Check concurrent work | /standup |
Recent peer activity, shared-file edits, and commit attribution |
| Speed up recall | /turbo |
Enable, inspect, or disable the shared warm search service |
These are Claude Code command names. In Codex, invoke the corresponding skill,
for example $session-cartographer:remember or $session-cartographer:turbo,
and describe the query or action. Project orientation replaces the retired
Cartographer /focus skill.
Additional skills: Codex's $session-cartographer:setup diagnoses local semantic
service access; /trustmap proposes Claude Code auto-mode environment settings
from recorded usage. See auto-mode guidance.
/carto opens the Explorer, a local web app over the same history /remember
searches. Each view below shows the same day of real work.
See what a day produced. 78 images written in 16 bursts across 7 sessions, above the events that wrote them. |
|
Open a burst. 17 images one session wrote between 5:15 and 5:50 AM, linked to the conversation that produced them. |
Pick a task back up. 31 tasks in the day, latest first, each with its project, agent, and last activity. |
Check a day against Git. 75 commits from 30 sessions across 18 projects, with a Markdown receipt to copy. |
Review what a session changed. The diff starts at the last commit before the session began: +46 −2 in Timeline.jsx.
|
Read the conversation behind it. 858 messages with tool calls folded, beside the documents and commits the session produced. |
Search every agent at once. 416 results from keyword and semantic ranking in 209 ms, faceted by project, event type, and agent. |
Browse every image sessions wrote. 728 from the last 7 days, read from 90 transcripts in 0.8 s and grouped by project. |
|
Public repositories keep their names. Other project, file, and session names
are replaced, and home directories read /home/demo.
Requirements: Node.js 22 or newer, bash, and jq. Node runs the hook launcher;
Git for Windows supplies bash on Windows. Every hook reads its payload with jq, and
without it the plugin installs cleanly but captures nothing. Install jq with
winget install jqlang.jq (Windows), brew install jq (macOS), or
apt install jq (Debian/Ubuntu). On Windows, Git Bash supplies bash. A
session started without jq prints a notice saying so.
Download and extract session-cartographer-<version>.tar.gz from
Releases, keeping the
extracted directory in a stable location. One bundle supports both agents.
Run the commands for your agent from that directory:
# Codex
codex plugin marketplace add "$PWD"
codex plugin add session-cartographer@session-cartographer
# Claude Code
claude plugin marketplace add "$PWD"
claude plugin install session-cartographer@session-cartographerA source checkout can be registered with the same commands.
Codex hook approval: launch the Codex CLI, run /hooks, select Session
Cartographer, and approve its hook definitions. Repeat when an update changes
those definitions. Start a fresh task/session after installation or approval.
Choose your history location. The corpus defaults to ~/Documents/dev.
Set CARTOGRAPHER_DEV_DIR in the environment used by your agent if your workspace
lives elsewhere. File edits, commands, and Git commit capture require the opt-in
CARTOGRAPHER_LOG_TOOL_USE=true. Logs can contain verbatim prompts and command
lines; keep them out of version control.
Read Adopting Cartographer for corpus ownership, project aliases, privacy, and resource use. Release installation covers bundle verification and upgrades.
Keyword search works immediately against captured events. Add local Qdrant and
an embedding server to search by meaning and recall indexed conversation turns.
Follow Setup; no Docker is required. In Codex, use
$session-cartographer:setup to diagnose access and request the necessary
loopback permissions. A sandbox-denied request does not establish that a service
is down.
From a source checkout:
npm ci --prefix explorer
npm run dev --prefix explorerIn a release bundle, the Explorer directory is
plugins/session-cartographer/explorer; use that path instead. Open
127.0.0.1:2527, or use /carto after installing its
dependencies. The UI binds to loopback only.
Timeline, search, sessions, and transcripts work without Turbo. The Memory Desk uses the managed Turbo backend and offers Start, Enable, or Refresh Turbo when needed. Opening the page directly does not start that backend.
Start with the context you need now: a decision to revisit, an investigation to
resume, or an idea you remember exploring elsewhere. Ask /remember a concrete
question, then narrow by project or date when useful:
/remember why did we change the retry policy
/remember --project my-app
/remember deployment --project my-app --since 7d
Search summaries are intentionally short. Follow the transcript to recover the conversation, or fetch complete event records from a checkout:
bash scripts/cartographer-search.sh "retry policy" --project my-app
bash scripts/cartographer-search.sh "lookup" --get evt-abc,evt-defRepeated searches in one session suppress previously served IDs; --all includes
them again. --transcript adds a raw-text fallback for conversations that have
not been semantically indexed. For older material, scope the date window rather
than treating an absent top result as proof that the history is missing.
For standing questions about the overall work, .carto/profile.md is a derived
corpus summary. Rebuild it with node scripts/build-profile.js. Project aliases,
bounded feeds for other agents, and briefings are described in
Project Registry & Briefings.
Real recorded activity, with project and file names replaced for these screenshots.
The Explorer's Memory Desk is an evolving workspace for returning to tasks and inspecting their evidence. It includes:
- A shared time range, project and text filters, and saved return points.
- Task and file browsing, linked activity charts, and transcript navigation.
- Current-file previews and Git diffs bounded by a session's recorded activity.
- Recall, showing searches, ranked results, and explicitly marked uses.
- Day, grouping a local calendar day's work by project and checking commits against Git, with a copyable Markdown receipt.
Session and file links preserve the selected context. File content is current; diff boundaries use commit times and can include other sessions' changes. Recent activity is evidence of an event, not proof that an agent is still running. See the work desk and Memory link reference.
The same digests are available without the UI:
node scripts/session-digest.js --session <session-id>
node scripts/session-digest.js --day yesterday --md/wrapup adds the reasoning hooks cannot capture: decisions, discoveries, and
open questions. It is useful for material sessions; ordinary sessions already
have their automatic history. /standup reports recent activity and file overlap;
shared-goal briefings and handoff records
remain planned.
Turbo keeps the search index in memory so each recall avoids rereading the corpus.
One setting covers both agents, in ~/.config/session-cartographer/config.json.
Use /turbo enable, /turbo status, or /turbo disable in Claude Code; in Codex,
invoke $session-cartographer:turbo and request the action.
Turbo starts disabled. The /carto skill enables it automatically on machines
with at least 16 GB RAM when the estimated index fits within 8% of RAM; otherwise
it leaves the choice to you. On machines below 16 GB, an enabled service defaults
to exiting after 30 idle minutes. Status reports the local memory estimate.
Ordinary recall uses the warm service through loopback HTTP or a private file
transport for restricted sandboxes. An unavailable or incompatible service falls
back to the portable CLI; --no-turbo forces that path. Exact record operations
such as --get stay on the portable path. The two backends can rank differently.
See Turbo Mode for behavior and evaluation.
Hooks capture future activity. To seed a new corpus, run these from a checkout
(or the release bundle's plugins/session-cartographer directory):
# Preview your configured authors' commits before importing; remove --dry-run to write.
bash scripts/backfill-git-history.sh --project my-app --since 2026-01-01 --dry-run
# Import native Claude Code and Codex memory into the event logs.
bash scripts/backfill-memories.sh
# Index historical conversation turns; requires Qdrant and the embedding server.
bash scripts/retro-index.sh --limit-days 30Native memory files remain authoritative; import does not edit them. Codex memory migration covers semantic indexing and refresh. Setup covers deeper reconstruction and older-data repairs; turn migration explains transcript indexing.
Claude Code / Codex hooks → shared JSONL event logs
├── /remember: keyword + optional semantic recall
├── Explorer: browse sessions and inspect work
├── digests and /wrapup: activity and judgment
└── Qdrant indexer: semantic event and turn search
The portable keyword scorer is bash + awk. The API has a separate JavaScript scorer. Both combine BM25 keyword ranking with optional Qdrant results through Reciprocal Rank Fusion. Transcript turns are grouped at indexing time; the original transcripts remain the source for full context.
The default configuration keeps capture, storage, search, and embeddings local. Hooks preserve provider provenance while both agents search the shared corpus. The co-occurrence graph uses structured project and procedure signals to support orientation and procedural recall.
Coverage depends on enabled hooks, retained transcripts, and completed imports. Keyword search has no exact phrase matching or stemming, and its tokenizer is focused on Latin scripts. Semantic search broadens matching but does not guarantee that every relevant session will rank. See scoring, rank fusion, and archival recall.
Cartographer records which results it serves and which agents explicitly use, and checks activity against source history. Evaluation covers retrieval, capture coverage, and adoption; these are separate measures.
Measurement history, findings, and fixes
Measured on the author's own corpus: one person's Claude Code and Codex work, March to October 2026.
| Result | How it was measured |
|---|---|
| 736 events, not 1. A scheduled agent asked ranked search what happened in a 24-hour window and got 1 event back. | A deterministic count over the same window found 736 events, 22 sessions, and 20 commits and pushes across four repositories. Counting is now its own API, and every count ships sample event ids so it can be checked with --get. See Facts. |
| 43 of 125 landed commits were missing from the session logs on 2026-09-26. | The day digest checks every logged commit against git; its 125 matched an independent git log count, repository by repository. Over 26–27 September, 23 of the 46 missing commits traced to a bug in the commit hook itself, which logged at most one commit per call; fixed in 0.8.1. See the changelog. |
| 287 of 1,350 Claude Code sessions (21%) called recall at all in the 30 days to 2026-10-15. Codex recalled in 1 of 59 sessions that saw the startup nudge. | Counted from Cartographer's retrieval telemetry, which records the session and call id behind every result it serves. Recall already answered quickly (p90 377 ms), so the gap was reach, not speed; recall now also ships as MCP tools. See MCP. |
| 9 of 60 records older than 90 days reached the top 10 when looked up by their own words; time decay let recent material outrank them. After the fix, 60 of 60. | scripts/age-curve.js on the live corpus on 2026-10-16: 204,341 events, 240 known items in four age buckets, 40 recency cases, semantic leg off. For the 90-day-plus bucket, the warm engine's top-10 hit rate went from 0.15 to 1.00, and recency stayed at 0.65. On a paired subsample of 30 cases, the portable CLI went from 0.23 to 1.00. A CI gate on a synthetic corpus now holds the curve. See Scoring. |
Use Node 22 for development and CI parity. The public unit suite is:
env -u CLAUDE_SESSION_ID -u CLAUDE_CODE_SESSION_ID -u CODEX_SESSION_ID -u CARTOGRAPHER_SESSION_ID \
node --test tests/unit/*.test.jsRead Testing for dependency setup, isolated browser tests,
packaging checks, and safeguards against writing test data into a live corpus.
tests/private/ is optional and is not needed by fresh clones or public CI.
To capture the Explorer with randomized names over your own activity, use the JavaScript screenshot tool.
- Provider architecture, log schemas, and custom hooks
- Explorer architecture and Internals
- Demo and evaluation and related projects
Search originated in a fork of Shreyas Patil's claude-code-session-bridge. The co-occurrence graph was inspired by DeepBlueDynamics' lume and the Semantic Knowledge Graph work of Trey Grainger and Erik Hatcher; Cartographer ranks structured session entities with Dunning's log-likelihood ratio (G²).
MIT. Notices for the adapted third-party code are in THIRD_PARTY_NOTICES.md.