← ClaudeAtlas

hadron-setuplisted

First-run setup for Hadron. Verifies prerequisites (node, tmux, free port), installs what's missing for the current OS, scaffolds a workspace, starts the server, and opens the dashboard. Use right after someone clones the repo.
zhaoyuda/hadron · ★ 1 · AI & Automation · score 72
Install: claude install-skill zhaoyuda/hadron
# Hadron Setup Goal: get a freshly cloned Hadron from zero to a live dashboard with a sample agent card (which the user can start), in a few minutes. You orchestrate; adapt commands to the user's OS. Confirm before installing system packages or starting long-running processes. ## 1. Preflight (deterministic) Run the bundled check — it installs nothing, just reports pass/fail: ```bash npm run setup:check ``` It verifies: **node ≥ 18**, **tmux ≥ 3.0**, **Claude Code on PATH**, the chosen port is free, and whether a `.hadron/` config already exists. Fix anything it flags before continuing. ## 2. Install what's missing Only for items the preflight flagged. Pick the right manager for the OS — **ask the user before running `sudo`**: ```bash # macOS (Homebrew) brew install node tmux # Debian/Ubuntu sudo apt-get update && sudo apt-get install -y nodejs npm tmux ``` Then project deps (always needed on a fresh clone): ```bash npm install ``` ## 3. Scaffold a workspace Ask the user which directory should be the workspace root (where `.hadron/` config lives and where agents work) and how they want to group agents. Then let the deterministic scaffolder write the config: ```bash node scripts/setup-workspace.js ~/work --name work --groups "Workers,Research" ``` This also installs a sample agent so the first screen isn't empty. Safe to re-run; it won't overwrite an existing config. ## 4. Start the server ```bash node server/index.js ~/work ``` Binds `127.0.0.1:3000` by defa