# AgentHub Internal SmartGift build. Local-first **control surface** for Claude Code agents — monitoring is one part of it, not the whole. Hooks POST every tool call to an Express + SQLite server and a React UI updates over WebSocket; **lanes** track parallel agent work through a pipeline; and the `agenthub` CLI drives real terminal sessions, lane runtimes, and Claude Code's own configuration. AgentHub records and shows — it does not orchestrate. The session in control makes every decision. Internal build — all rights reserved. *(Tiếng Việt: [README.vi.md](README.vi.md))* ## What it does - **Sessions, agents, events.** Everything Claude Code emits, recorded and searchable: tool calls, token usage, cost, subagent trees, transcripts. - **Lanes.** One lane per working directory, surviving session restarts. A lane moves through pipeline stages and the dashboard shows where it is. - **Stage detection.** The stage is inferred from the tool stream, so a session that never calls `agenthub stage` still shows progress — rendered dashed amber and never as done, because an inference is not evidence. - **Run Claude Code or Codex from the browser.** A real terminal (tmux + a real PTY, rendered with xterm.js) attached to a lane's directory — the exact TUI you'd see locally, fully interactive, resumable, and attachable from a real terminal too via `agenthub lanes shell`. Which CLI it starts is the lane's own setting. - **Analytics (in-dashboard tab), alerts, and a workflow view**, plus a CLI. ## Requirements Node **>= 20** (`engines` in `package.json`). Node **24** is what the test suites are verified on — node 25 currently breaks 6 server tests through a better-sqlite3 ABI mismatch and 20 client tests through a global `localStorage` change. The **`superpowers` plugin is required by the ship-feature pipelines only**, not by the dashboard. `/agenthub:ship-feature` and `/agenthub:ship-feature-lane` drive `superpowers:brainstorming`, `writing-plans`, `test-driven-development`, `requesting-code-review` and `verification-before-completion` phase by phase, and both built-in pipeline templates name those same slash commands as their per-node drivers. Without it the dashboard, hooks and CLI all work normally — the two pipeline skills are what stop partway. `/agenthub-doctor` reports it as a `WARN` row. **You do not normally have to install it.** The plugin's `SessionStart` bootstrap installs it for you, once, in its detached worker — so a session never waits on the clone, and the current session needs `/reload-plugins` before the skills resolve (any later session picks them up on its own). The outcome is logged to `~/.claude/agenthub/runtime/bootstrap.log`, and `/agenthub-update` retries a failed one. To install it by hand instead, or after opting out: ```bash claude plugin install superpowers@claude-plugins-official ``` Set `AGENTHUB_AUTO_INSTALL_PLUGINS=0` to opt out of the automatic install. Only the plugins on a fixed allowlist in `server/lib/skill-plugins.js` are ever installed this way — `superpowers` today. A custom pipeline template naming some other plugin's command is *reported* by `/agenthub-doctor` and never installed, because a template is a file anyone can drop into `DASHBOARD_PIPELINES_DIR`. ## Install as a Claude Code plugin Two commands on a machine that has nothing but Claude Code, no clone and no `npm run setup`: ``` /plugin marketplace add https://git.smartgift.io.vn/Smartgift-AI/AgentHub.git /plugin install agenthub@agenthub ``` The first session start installs the hooks, boots the server, puts `agenthub` on PATH; it runs detached, so the session never waits on it. `/agenthub-doctor` reports the state, `/agenthub-open` builds the UI and prints the URL, `/agenthub-update` refreshes after a plugin update. This path needs Node **>= 22.5** (no native `better-sqlite3`, so the server uses `node:sqlite`). Details, including what to delete on uninstall: [`docs/PLUGINS.md`](docs/PLUGINS.md). ## Install from a checkout ```bash npm run setup # root and client dependencies npm run build # builds the client into client/dist npm start # serves the built client and the API on :4820 ``` Open . Development, with hot reload: ```bash npm run dev # server on :4820, Vite client on :5173 ``` `DASHBOARD_PORT` overrides the port, `DASHBOARD_CLIENT_DIST` overrides where the built UI is served from (defaults to `client/dist`; the plugin install points it at its own runtime directory). `postinstall` writes the Claude Code hook entries that feed the dashboard — do not run it when the `agenthub` plugin is installed, or every event is counted twice. ### Run as a service (auto-start on boot) `npm start` only runs while that terminal (or `agenthub start`'s background process) is alive — a reboot loses it. On Linux, `agenthub service install` sets up a systemd `--user` service instead, so `:4820` is up again on its own after every reboot, with no manual step and no Claude Code (or any AI tool) needed to trigger it: ```bash npm run build # the service serves the built client, same as npm start agenthub service install # writes + enables ~/.config/systemd/user/agenthub.service agenthub service status # systemctl --user status agenthub agenthub service uninstall # disable and remove it ``` `agenthub service install` also tries `loginctl enable-linger` so the service starts on a cold boot, before anyone logs in; if that needs elevated rights on your machine it prints the `sudo loginctl enable-linger ` command to run once yourself. Plugin installs get the same persistence automatically — see [Auto-start on boot](docs/PLUGINS.md#auto-start-on-boot) in `docs/PLUGINS.md`. ## The CLI `agenthub` is linked by `npm run setup`; otherwise call `node bin/agenthub.js`. ```bash agenthub status # is the dashboard up agenthub start # start it in the background and wait for healthy agenthub service install # auto-start on boot via systemd --user (Linux) agenthub sessions # recent sessions agenthub lanes # lanes with stage and progress agenthub lanes pipeline # this lane's pipeline template, or switch it agenthub lanes node # run ONE pipeline node's own command (no id: list them) # (in a session: /intake, /qc, /ship-full, /ship-quick …) agenthub stage # declare the current lane's stage agenthub tail # live event feed ``` `agenthub --help` lists the rest. ## Lanes A lane is a working directory the dashboard watches. Two kinds: - **adopted** — a directory you already had. The dashboard only reads it; it is never reset or deleted. - **managed** — a git worktree the dashboard created under `LANES_ROOT`. It owns the full lifecycle and may reset or remove it, behind a three-check destroy guard and a counted preflight the caller has to echo back. ```bash agenthub lanes add --cwd /path/to/repo --title "My feature" # adopt agenthub lanes add --repo /path/to/repo --slug my-feature # managed worktree ``` Every lane also carries the CLI that drives it — `claude` (the default) or `codex` — picked in the Add-lane modal and fixed for the life of the lane. A Codex lane's run panel offers Codex's own sandbox, approval and reasoning-effort choices, and resumes with `codex resume --last`. Codex emits none of this dashboard's hooks, so a Codex lane records its runs but stays absent from Sessions and Analytics. Its **stage detection** works anyway, from Codex's own rollout journals on disk (`$CODEX_HOME/sessions/**/rollout-*.jsonl`, polled every `DASHBOARD_CODEX_POLL_MS` ms, default 15000), and on a Codex lane a detection also **advances the declared stage** — the one place an inference moves the blue `current` ring, because a Codex session has no hook and nothing else would ever move it. What a Codex lane cannot get for free is *evidence*: an auto-advanced node stays amber (`passed-no-evidence`), never green, since only the session itself can say what it finished. Three things help it get there: the run console pre-fills a codex pane's opening prompt with a stage-declaration checklist built from its own pipeline nodes, `agenthub lanes agents install` writes the same instructions as a marker-delimited block in the lane's `AGENTS.md`, and a 60s sweep (`DASHBOARD_CODEX_NUDGE_MS`, `0` disables) types a one-line reminder into a lane's pane if its current stage sits without evidence for more than two minutes. The declared stage comes from `agenthub stage`. The inferred stage comes from tool events and expires after `DETECTION_TTL_MS` (default 5 minutes), so a lane can move backwards between work sessions. Detection never writes the declared stage, and an inferred node never renders as done. A lane's pipeline template can be switched after creation — `agenthub lanes pipeline