Troubleshooting/Agent-Install: the ! incomplete row
A claude-jam-<port> directory with no session.json — a start that died before
it claimed a session. It used to be invisible to `sessions` and `clean`;
it is listed and cleanable now, once nothing holds its port.
Pairs with claude-jam 0ac2de5 (campaign F8).
wiki: how to look further back, and which of the three limits you just hit
Joining-a-Jam gains a "Scrolling back" section — PgUp/PgDn through the host's
REAL pane history, Shift+arrows a line, End/G/Esc back to live, the held-frame
count, and /history for the transcript. Guests get all of it: it is a read of a
screen they are already watching.
Troubleshooting leads with the complaint in the words people use it in ("I can
only see very little of this conversation") and a table that separates the
three limits behind it — what you were shown (--replay), what the jam still
keeps (--history, reached with /history), and how far the host pane's own
scrollback goes (2000 lines). Plus the honest ones: why the wheel does nothing
unless your terminal already sends wheel events, why a re-read page can be two
seconds stale, and that F2 no longer eats your scrollback.
wiki: the ten pages — install, agent-install, hosting, joining, remote, files, security, architecture, troubleshooting
Written against what actually shipped (README/MANUAL/SPEC 'what shipped' notes and
the real flags in the source). Everything specced but not built — LAN discovery,
sounds, nudges, upload auto-allow, guest scrollback, peer tasks, Windows — is listed
on Home under 'Not built yet' and described nowhere else.
Agent-Install is the page another person's agent is pointed at: the never-do list
first, then numbered non-interactive commands with a verification after each, the
steps that need a human called out, and a self-test whose expected output was
recorded from a real run on 2026-08-29.