Menu
Browse documentation

Start

Run your first agent

verified · v2026.5.29 edit on github
On this page 6 sections

With NullHub running, installing an agent is one command and a short wizard. This page takes you from an empty hub to a running NullClaw you can talk to.

1. Install NullClaw

nullhub install nullclaw

This runs a terminal wizard: it downloads the component, walks you through provider and API-key setup, and writes the instance config. The web dashboard at http://nullhub.localhost:19800 has the same wizard if you prefer clicking — installs are manifest-driven, so both paths produce the same result.

2. Start and check it

nullhub start nullclaw/<instance>
nullhub status

status shows every managed instance with its health. For a single instance, nullhub status nullclaw/<instance> prints the detail view. The dashboard shows the same as status cards, refreshed by periodic health checks.

Watch the logs while it boots — with a startup measured by the project at under 2 ms, don't blink:

nullhub logs nullclaw/<instance> -f

3. Talk to it

The agent binary is on your machine now, so you can use NullClaw's own CLI directly:

nullclaw agent -m "Hello, nullclaw!"
nullclaw agent            # interactive chat

For a long-running agent — chat channels, scheduler, HTTP gateway — the instance runs nullclaw gateway under hub supervision, listening on 127.0.0.1:3000 by default. If it crashes, the hub restarts it with backoff.

4. Add the rest of the stack (optional)

The same install command works for the other three managed components:

nullhub install nullboiler    # workflow orchestration
nullhub install nulltickets   # durable task tracking
nullhub install nullwatch     # traces, evals, cost

The wizard links components as it goes — a local NullTickets gets wired to NullBoiler automatically. Then bring everything up at once:

nullhub start-all
nullhub status

What just happened

NullHub read each component's nullhub-manifest.json, which describes installation, configuration, launch, health checks and wizard steps. The hub is a generic engine that interprets manifests — which is also why it only manages components that publish one (NullClaw, NullBoiler, NullTickets, NullWatch today).

Next steps