Repository navigation
Releases
Releases · UurDemir/agent-hub-ui
v0.4.1
Run it without cloning: npx agent-hub-ui
Changes since 0.4.0
- A reporter pointed at a hub's dashboard port instead of its ingest port now says so: "… isn't a hub's ingest port. If that's the hub's dashboard, report to its ingest port instead (default 4318)". Before, it said "The hub rejected this machine's key (HTTP 401)", which sent people looking for a key problem that wasn't there.
v0.4.0
Run it without cloning: npx agent-hub-ui
Changes since 0.3.0
- Container image for the hub:
ghcr.io/uurdemir/agent-hub-ui(amd64 + arm64), for running the hub on a NAS or home server. See "Running the hub in a container" in the README. AGENT_HUB_MACHINES: a hub can take its machines as JSON in an environment variable instead of a keys file, so a container needs no mounted file. Unlike a keys file, it is read only at startup.- Breaking: a dashboard on any address other than loopback (for example
--host 0.0.0.0) now refuses to start without--viewer-password. Before, only a hub did, so a plain dashboard served transcripts to the network without a login. The default127.0.0.1is unchanged.
v0.3.0
Run it without cloning: npx agent-hub-ui
Changes since 0.2.1
- Message running sessions (
--allow-send): send text to a live Claude Code session through Claude Code's own local messaging socket. Only the tab opened at start can send; other tabs need the one-use link printed in the terminal. Sends are shown asYOU · HUBin the timeline. (#1) - Many machines on one dashboard (opt-in): run one Agent Hub with
--hub, and have other machines send their agents to it with--report-to. (#2)- Each machine has its own key, created with
--new-key <name>. The hub stores only key hashes and re-reads the keys file when it changes, so removing an entry revokes that machine. - Each machine picks what it shares with
--share metadata|activity|full(defaultmetadata), and the hub can only lower it. That machine's dashboard shows a "Reporting to …" badge. - The hub dashboard stays on
127.0.0.1behind your SSO reverse proxy (--allowed-host), or uses--viewer-password. - New UI: a machine filter, a Machines section, and machine labels on cards, lanes, the detail panel and the canvas.
- Each machine has its own key, created with
- Nothing leaves your machine unless you pass
--report-to, and sending to sessions only happens with--allow-send.
See the README section "Many machines on one dashboard" for setup.