Skip to content

v0.10.0: team hub admin, alerts that reach you, one-command hooks for every harness

Choose a tag to compare

@JamesMoriartyDecripto JamesMoriartyDecripto released this 13 Oct 15:33
90ad813

Added

  • Hub › Admin (#93), on the hub machine only: add a sender (token and connect line shown once), pause, resume, revoke by typing its id; viewers; cadence per sender; budgets; alert switches; retention days and delete-before with a preview count. Every change writes a line to admin-audit.jsonl (0600, never a token); remote requests get 404. The privacy profile wizard waits for #85.
  • Hub alerts (#94): an always-on machine gone silent, monthly spend at 80% / 100% of a budget (USD, per project or global), an error spike (over 3× the 7-day hourly median, at least 5), a token used from a new host. A ⚠ n pill in the top bar and the library header opens Hub › Alerts; ack and snooze (1 h / 1 d) from the hub machine only. Rules switch off per name in config.json alerts; budgets are documented as USD, the history's currency.
  • Schema: a files entry can be { path, optional: true, description } for a file a run writes: while it is missing, validate and the PDF checks stay quiet and the Inspector shows it as "not generated yet". The report-studio example uses it for the tower-documentation PDF (#137).
  • The satellite relay recovers by itself (#188): connect, a new token or a role change apply to a running library within 5 s (no restart); a refused or paused token keeps the queue, asks again every 30 s and delivers the queue on the first accepted answer; Send test asks at once. The hub tells a paused machine apart (401 with state: "paused", shown as held / "paused by the hub") from a refused token, without telling a wrong secret whether an id exists. The library prints one line per relay state change.
  • flow-tower hooks install (#189): one command wires Claude Code, Codex, Pi and Hermes on this machine (or a project with --project), on the port of the running library; it keeps the user's own hooks, backs up each changed file, and replaces older hand-made Flow Tower entries instead of duplicating them. hooks status shows where they are wired and flags a stale port or Node path; hooks uninstall removes only Flow Tower's entries. connect ends with the hint. Replaces the 11 hand edits the satellite setup needed.
  • Shared towers are validated (#190): a tower with an error is not sent and the hub keeps the last valid version (it also refuses a structurally broken upload with 422). The teammate sees 1 tower not sent on the SAT chip and each shared tower's state in Settings › Sharing, including a warning when a sync removed nodes that events may still name. The hub card says updated <time> ago; files a share does not carry (missing, or outside the share folder) are info on the hub, not errors. share --files carries the agent folders a tower references (.github/, .claude/agents|skills|commands/, .agents/, .codex/prompts/); share no longer adds a folder already covered in the library.
  • Hub alerts reach the lead outside the tab (#191): the hub checks the rules every minute and sends each new alert, and its clearing, to an optional webhook (notify: ntfy, Slack, Telegram or JSON; set and tested from Hub › Admin › Notifications, url masked, never logged); Hub › Alerts can show browser notifications. A new errors rule fires when a machine sends 3 errors in 15 minutes (alertThresholds.errors), so a new team sees its first failures without a week of history.
  • Harness parity (#196, #5): tests/harness-parity.test.ts replays one session through every adapter (Claude Code, Agent SDK, Codex, Pi, Hermes, emit), checks the normalised events and that one match: rule lands each harness's shell call on the same node; what a harness cannot send is declared with its reason (table in docs/realtime.md). Pi was checked with a real run (extension and --mode json): JSON mode now keeps the session id on every line, drops streaming chunks, shows tool results as text and usage with the model and token detail. The Agent SDK integration also sends SessionStart, SessionEnd and Notification.
  • Hub › Now answers who, where and what (#192): one row per machine and session with the tower and node it works on, its state, and the last error (node or tool and age, never event text); a click opens that tower on that node. The library header shows ● n working. Consistent signals: the tower file's validation chips read YAML n ERR/WARN, a red LIVE n ERR counts live errors, a failed tool shows ✕ in the feed, HUB n/m counts active senders only, token add refuses an id in use, CLI token changes are written to the admin audit log (via: cli), and the Live feed sits beside the Hub panel instead of under it.
  • A team without Tailscale has one documented route (#193): integrations/hub/Caddyfile.hub puts Caddy in front of a full hub (events, heartbeats, OTLP and shared towers; the owner views over SSH), with steps in the kit README. The CLI's hints print node <checkout>/bin/flow-tower.js when flow-tower is not on PATH; token add prints the connect line for the other machine; the hub warns about the kit's example placeholders left in config.json; copy --list marks the examples that point at this repo; the library footer says how to add towers in a library or on a hub.
  • flow-tower service install|status|uninstall (#194) keeps the local library running at login (systemd user unit on Linux, launchd agent on macOS), so a teammate's events are not lost when they forget to start it; connect suggests it when no library runs. On a satellite, emit posts to the running library, falls back to the hub when the library refuses the connection, and posts straight to the hub when no library is recorded: never to a default port (a test event on the test server reached another server that way before the fix).
  • Second newcomer dry run fixes (#206): Hub › Admin PAUSE and RESUME work (they got 415); on a hub a teammate's events light only that teammate's shared towers and the hub's own, never another teammate's; the main agent is main in every harness, so one agent:main rule fits all; Hub › Now follows the session (idle after the agent stops, ended after the session, then dropped); H opens the Hub panel on the first load (the library filter no longer takes the focus; / does); service install refuses a port a library already uses and service status tells an installed unit that is not running; the hub card says newer version not sent when a teammate's latest save was refused; the kit lists the full-hub Caddy route in step 4 and says to create a token before a hub without viewers starts.

Changed

  • Example towers follow the team-UX work (#187-#196): team-hub gains the local port file and stream ids, hooks install, service install, the relay supervisor, the share sync and the hub's shared-towers guard, the alert webhook and the Now view (36 nodes, audit clean); command-center shows the four teammate steps for any harness, Caddy for a team without Tailscale (deploy/Caddyfile.hub), the alert webhook and the token approval; dev-squad's coder never rewrites an existing test file, an empty grader answer is never a pass, and the verifier holds a user-facing change no test exercises end to end.
  • Docs: docs/architecture.md is split into four maps that each load whole: core, documents and reports (architecture.md), server and hub, CLI, app. docs-qa Q24 (which file owns the per-sender tokens) passes again, 3/3; the docs-qa report is refreshed: 28/31 (#143).

Fixed

  • Hub alerts could not see hook errors (#187): history dropped every tool.end as a replay of its tool.start (same call id), and kind: error events were stored without an error status, so the error spike never fired. Both now count.
  • Hub › Admin showed always-on for a sender with no cadence, while the alerts treat it as on-demand; it now shows what applies, and a new sender starts as on-demand (#187).
  • emit and npm run simulate post to the server the user folder runs, on whatever port, instead of 5317 when no --url is given: a satellite's SessionStart hook could reach another server on 5317 (#187). The copy hint no longer prints a 5317 URL.
  • Two e2e tests were wrong: the /api/file check asked for optional files not generated yet (#137), and the voice hub-phrase test faked a hub without answering the alert pill route added by #94.

Release gates: examples/release-auditor/reports/v0.10.0.md