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

Files

T

nntrivi2001 c7dbaf2d9f refactor: finish the AgentHub rename and drop the MCP server

Two leftovers from the rebrand, done together because they touch the same
docs and manifests.

**Data directory.** `agent-dashboard` could not simply be renamed in the
source: it names a real directory holding the live SQLite database. Startup
now moves it once, via `migrateLegacyDataDir()` in `server/lib/claude-home.js`
— a same-filesystem rename, so it is instant even at multiple gigabytes and
cannot leave two divergent copies. `getDataDir()` stays PURE and resolves to
the legacy path until the move happens; the first version of this put the
rename inside the getter, which meant `npm run test:server` relocated the
developer's real database as a side effect. The call sits behind
`require.main === module` and ahead of the router requires, because those pull
in db.js, which opens SQLite at module load. A failed rename is silent and the
old directory keeps being used: an unfashionable directory name beats a blank
database beside an unreachable one. Same treatment for the port-discovery file
(`.agent-dashboard.json` → `.agenthub.json`, old one dropped on write).

Not renamed on purpose: the Sagi localStorage keys (renaming silently resets
everyone's prefs) and the PWA manifest `id` (changing it orphans an installed
app).

**MCP server.** 4 tool calls in 46 days across 577,132 events, against 4,556
lines of TypeScript, a 2 MB committed build artifact, and a pre-commit guard
that had already blocked commits twice. Deleted: `mcp/`, the maintainer skills
and `mcp-reviewer` agent, the build check, `plugins/agenthub/.mcp.json`,
`docs/MCP.md`, 12 npm scripts, 5 Makefile targets, and every doc section
describing it.

Kept, because they are unrelated things sharing the name: the Config
Explorer's MCP tab and its API, per-lane Playwright MCP, the agenthub-config
plugin's MCP audit, and the historical `mcp__plugin_agenthub_*` events that
analytics must keep attributing.

Verified: server 1432/1432, client 459/459, tsc clean, prettier clean. Both
directions of the migration proven — a sandbox-HOME test run leaves the legacy
directory untouched, and a real boot moves it with its contents intact.

2026-09-08 09:48:40 +07:00

1.4 KiB

Raw Blame History

description

description
Diagnose a plugin-installed AgentHub — Node, bootstrap, server, hooks, CLI

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 or FAIL Runtime deps → run /agenthub-update, then check ~/.claude/agenthub/runtime/bootstrap.log and server.log.
WARN agenthub CLI → print the exact export 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-update retries it, and print the claude plugin install … line from the output as the manual route.
WARN Dashboard UI → run /agenthub-open to build the bundle.

No preamble, no summary of things that passed.

1.4 KiB Raw Blame History

1.4 KiB

Raw Blame History