Build it. Make it yours.
Work on the hub, dashboard, or documentation site without coupling their deployments.
Run the hub and dashboard
Cargo tests cover the native hub, store, command line, and protocol. Build the dashboard before serving it in production. For local dashboard development, Vite proxies /api to the local hub or AGENT_HUB_URL. Recompile Rust after editing a dashboard component.
cargo test
cargo run -p agent-hub -- serve
# In another terminal
bun run dev
# After editing dashboard Rust
node rust-js/tooling/cli.js build --package dashboardCopyWork on this site
The site uses Next.js App Router through the rust-js bindings, React, and plain CSS. site:dev first compiles the Rust and starts Next.js. After changing website/**/*.rs, run site:compile in another terminal; Next.js picks up the generated JSX with Fast Refresh. Routes and layouts live in website/app/, shared components in website/components/, and documentation content in website/lib/. Generated JSX and declarations are committed alongside Rust, just as for the dashboard.
bun run site:dev
# After editing website Rust
bun run site:compile
# Production build and local preview
bun run site:build
bun run site:previewCopyDeploy to GitHub Pages
This site is static and independent of a running hub. Enable Pages in the repository's Settings → Pages, choose GitHub Actions as the source, then run the Deploy documentation workflow manually. It builds the committed generated JSX with Next.js and deploys website/out. Recompile Rust and commit its generated files before deploying changes. Next.js basePath and trailing-slash directory exports support the repository subpath without server rewrites. Run Playwright tests locally before deploying; the workflow does not run tests.
bun run site:build
# The deployable static artifact is website/out/
# Workflow: .github/workflows/pages.ymlCopyUpgrade the hub
Update the checkout, rebuild the dashboard, and reinstall the native command. Replace the existing hub, preserving the --listen and --db values it used. Existing agent watches reconnect and the saved history remains available.
git pull
bun run build
cargo install --path agent-hub
agent-hub serve --replaceCopyWhen something does not connect
If the client cannot reach the hub, verify AGENT_HUB_URL, the hub process, and its listener. Across machines, check Tailscale connectivity and try the private IP if the hostname does not resolve. A build-version notice means the client and running hub differ; reinstalling the command alone does not replace the hub process. If the dashboard is missing, run bun run build in the checkout the installed command was built from.
echo "$AGENT_HUB_URL"
tailscale status
agent-hub agents --as codexCopy