Install: npm package is @roypadina/claude-jam (the command is still claude-jam)
Install: say that npm 404s, and give the tarball route that works today
The page presented `npm i -g claude-jam` as the install command and as "the
only Windows path". The package has never been published, so it 404s — and
the release doc-drift check runs these commands rather than reading them.
Says NOT YET PUBLISHED at the command now, with the `npm pack` +
`npm i -g ./claude-jam-0.23.0.tgz` route beside it, and the reason that route
is a fair rehearsal rather than a workaround: identical package, identical
`files` list, identical `bin` shim. The Windows block gets the PowerShell form
of the same thing. Upgrade/uninstall lines are marked "once published".
Verified by running it on macOS into a throwaway --prefix: the shim resolves
to cli.mjs and prints the launcher's usage.
Install: npm, and the Windows client stated honestly
v0.32 W1 landed a native Windows CLIENT. The page said "macOS and Linux.
There is no Windows build", which is now wrong in both directions: hosting
is macOS/Linux (or Windows through WSL2), joining includes Windows
natively.
What the new section refuses to say is "Windows supported". It is
implemented, unit-tested on a real windows-latest runner on every push, and
has never been run by a human — no toast seen, no sound heard, no key
pressed in Windows Terminal, no jam joined. Whoever tries it first is doing
the verification, so the page asks them to report what happened.
Also: npm as an install path on every platform (the only one on Windows),
the prerequisites table corrected to say tmux and claude are what a HOST
needs, and the Windows spellings of the state and history paths with the
ACL that stands in for 0600 there.
NOT PUSHED.
docs: two lines the 0.21.1 gate's doc check found wrong
Install: `npm install` pulls FIVE runtime dependencies, and the sentence said four
while listing five (ws, ink, react, @inkjs/ui, ink-text-input).
Agent-Install: the expected `claude-jam host` output omitted the `shared-session
contract → …/system-prompt.txt` line, which host.mjs prints unconditionally (only
--no-system-prompt replaces it with a different line) — so an agent following the
page literally sees an unlisted line and has to decide on its own whether the check
failed. Added, with a note that `claude profile:` appears only when
CLAUDE_CONFIG_DIR is set.
Both re-run end to end on 2026-08-30 against the 0.21.1 tree, including
`claude-jam end agentcheck`, exit 0, tmux session gone, state dir removed.
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.