cc-readback

What it does

• Ask Claude Desktop what your terminal sessions did today, which one is blocked on you, when a decision was made, or which files a session touched
• Four tools: briefing, list_projects, list_sessions, get_session_digest — read-only views of the record already on disk
• Secret redaction on every returned string; tool output, thinking blocks, attachments, pastes, and keys are never read
• One-click .mcpb for Claude Desktop, plus registration with Claude Code at user scope from the same installer

When to use it

For developers who live in Claude Code in the terminal but keep a Claude Desktop window open: get a cross-session briefing — what shipped today, what is waiting on a decision — without grepping ~/.claude/projects by hand.

Getting started

# Requires Node 22.13+; Claude Desktop and/or Claude Code
# One click (Desktop): open the .mcpb from GitHub Releases
#   (Settings → Extensions), then fully quit (Cmd-Q) and reopen Desktop

# From source (Desktop + Claude Code):
git clone https://github.com/affirmitv/cc-readback && cd cc-readback
npm install && npm run build
node dist/cli.js install all

# optional: skip Desktop tap-to-approve
# { "permissions": { "allow": ["mcp__readback__*"] } } in ~/.claude/settings.json

Things to know

The npm install form is still listed as 'once published' in the README, so use the .mcpb or source route today. It is a read-only view of history, not memory and not sync — it shows what Claude Code chose to write to disk, nothing more.