29858ddccb
The READMEs never said tmux was needed, so a fresh install only found out when Start Run failed with nothing explaining why. Both doctors were silent about it too. - README/README.vi: a prerequisites table (node, npm, git, tmux, claude, codex, gh, systemd) and per-OS tmux install + verify steps; the feature list is regrouped into observe/drive/configure and now covers analytics, alerts, import, remote sources, the config explorer and Update all. - INSTALL: Step 0 for the system packages, plus a troubleshooting entry separating "tmux missing" from "the server has a different PATH". - SETUP/docs/README: the same troubleshooting entry and a pointer to Step 0. - plugin-doctor: a tmux row, WARN and never FAIL - the run console and `lanes shell` break without it, nothing else does. Reuses tmux.js's own isTmuxAvailable(). - agenthub doctor: asks GET /api/run/tmux instead, because the PATH that decides whether a run starts is the server's, not the caller's shell's.
2.2 KiB
2.2 KiB
description
| description |
|---|
| Diagnose a plugin-installed AgentHub — Node, npm, disk, bootstrap, server, hooks, CLI, tmux, UI build |
Run the diagnostic and report what it found. Do not fix anything unless the user asks.
node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-doctor.js"
Print the output verbatim, then add at most three lines of guidance based on the
FAIL and WARN rows:
FAIL Node→ the installed Node is too old fornode:sqlite; the server cannot start until Node is upgraded.FAIL Hooks→ duplicate hook entries double every token and cost figure. Starting a new Claude Code session removes them automatically (the bootstrap backs the file up assettings.json.agenthub-bakfirst).FAIL Server→ run/agenthub-update, then check~/.claude/agenthub/runtime/bootstrap.logandserver.log.FAIL Runtime deps→ the install is incomplete, not merely absent. Delete~/.claude/agenthub/runtime/node_modulesbefore running/agenthub-update; reinstalling over the broken tree is what let it survive.FAIL npmorFAIL Disk→ nothing else in the report can be trusted until these are fixed; both silently truncate installs.WARN agenthub CLI→ print the exactexport PATH=...line from the output.WARN Skill plugins→ the pipelines name slash commands no installed plugin provides. The dashboard is unaffected;/agenthub:ship-feature(-lane)is what stops partway. The bootstrap normally installs these itself, so this row also means that attempt has not run or did not succeed — say/agenthub-updateretries it, and print theclaude plugin install …line from the output as the manual route.WARN tmux→ only the run console,agenthub lanes shelland the session-reload keystrokes are affected; monitoring, lanes and the CLI are not. Print the install command from the output. If the row saysokbut Start Run still fails, the server has a different PATH than this check — ask it directly withcurl -s localhost:4820/api/run/tmux.WARN Dashboard UI→ run/agenthub-opento build the bundle. When the row quotes a build error, report that error — it is the actual problem.
No preamble, no summary of things that passed.