cctop / Panel guide / Files

§7FilesNoteLine counts come from git; outside a repository the column stays empty.

Files

Every file this session touched, how much changed, and which reads were wasted re-reads.

Touches

reads as
R×6 E×5

What it means: The blast radius of this session — every file it read, edited, or wrote, independent of what git ends up showing.
What to do: Useful for a quick review of what a session actually touched before deciding what to commit.
Measured: count · from file tool calls · exact · how

Lines ±

reads as
+210 −31

What it means: Lines added and removed per file, from git — the real size of the change, not just the file count.
What to do: A file with disproportionate churn relative to the stated task is worth a second look before commit.
Measured: lines · from git · exact · how

Uncommitted

What it means: git diff --numstat HEAD (added, removed, files) and the last commit Claude Code summarised (gitOperation.commit) with the edits since it
Measured: lines · from git · the transcript · exact · how

Rewind points

What it means: file-history-snapshot lines in the current turn (checkpoints /rewind can restore) and the Bash writes of the turn no checkpoint covers; per file: the checkpoint version (file-history-delta, ⚠ at v8+), IDE edits (edited_text_file), stale markers (staleRecovered, staleReadFileStateHint), edit → re-read → edit churn
Measured: count · from the transcript · exact · how

Re-reads

reads as
re-read ⚠

What it means: Re-reading a file that hasn't changed re-injects the whole thing into context for zero new information.
What to do: Three or more re-reads is flagged ⚠ — point the model at a narrower range, or ask it to keep its own notes instead.
Advisor: A04 Re-reads
Measured: count · from file tool calls · exact · how