Documentation · v0.1

Get started in 30 seconds.

Superview is a local CLI. Install it once, run sv, and every Claude Code session on your laptop becomes browsable.

01 Install

One command. No account.

Superview ships as a single npm package. It runs entirely on your machine — no signups, no API keys, no telemetry.

Recommended · global install
~/ — install
$ npm install -g superview@latest

added 1 package in 4s

$ sv --version
superview 0.1.4

After install, the binary is available as both sv and superview. Use whichever you prefer.

No-install · one-off run
~/ — npx
$ npx superview

Skips installation. Slower first run, but useful for trying it on a fresh machine.

Node
≥ 18.0.0
OS
macOS · Linux · Windows (WSL)
Claude Code
v0.x — auto-detected
02 First run

Type sv. That's it.

Superview auto-detects your Claude Code session directory (~/.claude by default), indexes every workspace, and drops you into a browsable terminal UI.

~/dev — sv
Superview welcome screen on first run

Use ↑ ↓ to navigate, enter to drill in, q to quit.

What you'll see

A · workspaces

Every Claude Code project, ranked by recent activity.

B · signals

Edit thrashing, error loops, abandoned runs — flagged inline.

C · timeline

Every tool call, file edit, and error in chronological order.

03 Commands

The whole CLI fits on a postcard.

Five flags. Two aliases. No config file required.

sv
Open the dashboard.
sv --version
Print version and exit.
sv --help
Show all flags and shortcuts.
sv scan
Re-index all sessions. Run after a long offline period.
sv scan --since 24h
Only scan sessions modified in the last 24 hours.
sv export <workspace>
Dump a workspace's signals as JSON. Pipe into anything.
sv --path ~/custom
Override the Claude Code session directory.
04 Examples

Real things people do with it.

a · triage

Find the session that went off the rails.

Open Superview, sort by signal severity. The workspace with the loudest red dot is where Claude got stuck. Drill in to see the exact tool call that started the loop.

$ sv
→ press s to sort by signals
~/dev — sv
Triaging signals
b · review

Read the trajectory before you push.

Before opening that PR, spend 30 seconds in Superview. See every file Claude touched, every tool call it made, every error it silently retried. You'll catch surprises GitHub never shows you.

$ sv
→ enter on workspace · scroll the timeline
~/dev — sv
Reviewing a session timeline
c · pipe

Pipe signals anywhere.

sv export dumps structured JSON. Send it to Slack, store it in a database, or build your own dashboard. Local-first doesn't mean isolated.

~/dev — pipe
# Slack-ready summary
$ sv export acme-app | jq '.signals[] | select(.severity=="high")'

# Daily digest in cron
$ sv export --since 24h --all > ~/digest.json

Ready?

Run it once. You'll keep it open.

$ npm install -g superview@latest