Where Was I

WhereWasI

Claude forgets everything between sessions. What you were doing, what's next, what broke — gone the moment you close the terminal.

WhereWasI fixes that one thing well. Open a project tomorrow and the first thing you see is the last task you were on and the next step — so you pick up immediately. Per-project, automatic, no config.

This is not a memory bank. No search, no recall by topic, no accumulated history. Just the current state, to the point.

What you see

When you open Claude Code (or Codex CLI) in a project, WhereWasI injects a short resume at the top of the session:

# where was i: wherewasi  ·  branch wherewasi-v2

Last: Rewriting docs for the resume pivot (README + architecture).
Next: Run the full test suite + ruff, then deploy with install.sh.

3 uncommitted · a1b2c3d docs rewrite

Two load-bearing lines — Last (where you were) and Next (what to do) — over one compact git line for grounding. No file dumps, no stale error echoes (you have git for that). Zero latency: it's read from a file, no LLM call at open.

How it works

WhereWasI is files + hooks. No database. One Markdown file per project at ~/.claude/wherewasi/resume/<cwd-slug>.md (the cwd path, slashes turned to dashes), refreshed as you work:

1. Every 25 prompts (UserPromptSubmit, no LLM) — a cheap refresh of the git line (branch, uncommitted count, last commit). Your Last/Next narrative is preserved.
2. On compaction (PreCompact, LLM) — claude --print reads the transcript tail and rewrites Last + Next from what you were actually doing.
3. On session end (SessionEnd, LLM) — rewrites Last + Next when you leave, so a short session that never compacted isn't stale the next time you open. Runs detached, so it never delays your exit.
4. On session start (SessionStart) — the resume file is read and injected (with git refreshed live). First time in a project? You get a minimal git-derived resume so you never open blank.

Replace semantics: the file always reflects the current state. No history accumulates.

Install

Requirements: Claude Code and/or Codex CLI, python3 (stdlib only — no uv, no pip, no deps).

As a Claude Code plugin (recommended):

# In Claude Code:
/plugin install wherewasi@sebastianbreguel/wherewasi

Or clone and run the installer:

git clone https://github.com/sebastianbreguel/wherewasi.git
cd wherewasi && ./install.sh

Use the marketplace install OR ./install.sh, not both — each registers the hooks separately, so doing both fires every hook twice (and pays the compaction LLM cost twice).

Codex CLI (also supported): ./install.sh auto-detects ~/.codex (or $CODEX_HOME) and wires Codex too. Codex hooks share Claude Code's JSON stdin/stdout wire protocol, so the same wherewasi.py runs unchanged. It needs [features].hooks = true in ~/.codex/config.toml, and Codex may prompt to trust the hook on first launch. Resume state is shared with Claude (one ~/.claude/wherewasi/resume/<slug>.md per project), so switching between the two on the same repo shows the same "where was I". Note: Codex has no SessionEnd event, so the end-of-session LLM rewrite is skipped there — PreCompact + the rolling git refresh keep it fresh.

First session in a project: you get a minimal git-only resume. After you've worked a bit: the resume fills in with your last task + next step.

# Uninstall (also cleans up legacy engram data, if any)
cd wherewasi && ./uninstall.sh

Commands

python3 ~/.claude/tools/wherewasi.py --cwd "$PWD"          # print this project's resume
python3 ~/.claude/tools/wherewasi.py --reset --cwd "$PWD"  # clear this project's resume

Or use the slash command: /wherewasi (show) · /wherewasi --reset (clear).

Privacy and transparency

Everything lives in ~/.claude/wherewasi/resume/<cwd-slug>.md (plain Markdown). Nothing leaves your machine except the one LLM call below.