AgentHub/plugins/agenthub/commands/agenthub-doctor.md at c507d37baf68a027353f1ac8b6fff6fa0d2ee74b

Files

T

nntrivi2001 5b3884b309 feat(ui): call lanes "workspaces" in the UI, CLI output and docs

Copy-only rename (workspace redesign, phase 0). The word a user reads
changes — "Lane" → "Workspace", "Add lane" → "Add workspace" — in both
locales, in agenthub CLI prose and help, in the server's error messages
and in the docs. Every identifier stays: /api/lanes, `agenthub lanes`,
--lane, AGENTHUB_LANE_ID, error codes, tmux names, DB tables, file,
component and i18n key names. docs/LANES.md keeps its name, retitled
"Workspaces (lanes)".

2026-10-01 16:03:24 +07:00

2.1 KiB

Raw Blame History

description

description
Diagnose a plugin-installed AgentHub — Node, npm, disk, bootstrap, server, hooks, CLI, systemd, 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 for node: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 as settings.json.agenthub-bak first).
FAIL Server → run /agenthub-update, then check ~/.claude/agenthub/runtime/bootstrap.log and server.log.
FAIL Runtime deps → the install is incomplete, not merely absent. Delete ~/.claude/agenthub/runtime/node_modules before running /agenthub-update; reinstalling over the broken tree is what let it survive.
FAIL npm or FAIL Disk → nothing else in the report can be trusted until these are fixed; both silently truncate installs.
WARN agenthub CLI → print the exact export PATH=... line from the output.
WARN systemd → when it says the unit names a previous plugin version, the dashboard is running now but will NOT come back after a reboot. Starting a new Claude Code session repairs it; print the --force command from the output as the immediate fix. "installed but not running" just needs systemctl --user start agenthub.
WARN tmux → only the run console, agenthub lanes shell and the session-reload keystrokes are affected; monitoring, workspaces and the CLI are not. Print the install command from the output. If the row says ok but Start Run still fails, the server has a different PATH than this check — ask it directly with curl -s localhost:4820/api/run/tmux.
WARN Dashboard UI → run /agenthub-open to 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.

2.1 KiB Raw Blame History

2.1 KiB

Raw Blame History