It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
Version
0.1.0
License
MIT
Repo stars
3
Last change
2026-10-10
What it can reach
Draws in the session
Claude Code 2.1.288 or later; the author says the function-hooks API is early access. Jumping between prompts with /where-were-we up and down works in the fullscreen layout. /where-were-we count sets how many prompts are listed, 6 by default, and /where-were-we greeting turns the startup recap toast on or off.
The marketplace, scarrillo, also holds release, a Claude Code plugin, and pr-review-cycle, a skill. Finding your way back through a session is why this page files it under workflow. prompt-rail, by oikon48, draws a rail of the session's prompts where a click jumps to one. recap-plus, by skanehira, draws a recap of what the session is for and what comes next. This one puts the time before each prompt in the transcript, with the date for older ones, prompts from resumed sessions included. /where-were-we lists recent prompts with dates and times, and /where-were-we last shows the previous session's last prompts and the command to resume it. It reads this session's transcript and this project's entries in Claude Code's history.jsonl, prompt text only, and the README says it doesn't access the network or change your project files.
Demo
Screenshot of the author's GitHub page.
What it hooks into
session.startWhen a session starts
classic.SessionStartA Claude Code event
classic.UserPromptSubmitA Claude Code event
session.appendWhen an entry is written to the transcript
turn.completeWhen a turn ends
session.endWhen a session ends
command.runWhen you run its slash command
ui.renderDraws into the sessionUserMessagePromptHint
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Files
The author's README and source, 4 files. They load when you open them.