@huynle/hub 0.7.3 → 0.8.0

package/CHANGELOG.md

@@ -2,6 +2,235 @@
 
 ## Unreleased
 
+## 0.8.0
+
+Workspaces, supervision, split panes and side chats, shared agent profiles, persistent AI-powered artifacts, teams,
+and the Watchtower. All new state is additive. Cluster hubs need `hub-server migrate` (schema v2) before the new
+pods start. See [docs/operations.md](docs/operations.md) for the rollout, rollback, backup and front-proxy notes.
+
+### Fork and revert a message
+- Hovering (or focusing) one of your messages in the console shows **Copy · Fork · Revert**, like the OpenCode app;
+  on a phone, long-press it or tap its ⋯ button. **Fork** opens a new session with the conversation before the
+  message and the message in its composer. **Revert** hides the message and everything after it, restores the files
+  the session changed since then (confirming first, with the list), and puts the message back in the composer; a
+  banner offers **Restore**; sending the next message makes it permanent. Works across devices and in panes.
+- New console routes (user-only, audited): `POST /api/sessions/:id/fork`, `GET …/revert/preview`, `POST …/revert`,
+  `POST …/revert/restore`, `POST …/revert/commit`. Spoke features `fork` and `revert` (OpenCode processes that reach
+  their own server) with ops `fork`, `revertPreview`, `revert`, `revertRestore`, `revertCommit`; a staged revert is
+  reported as `SessionInfo.revert` (additive: older hubs ignore it). Other harnesses show the actions disabled
+  ("not supported yet"). Contract: [docs/session-view.md](docs/session-view.md#fork-and-revert-a-message).
+
+### Workspaces and supervision
+- **Workspaces** ([docs/workspaces.md](docs/workspaces.md)): durable, cross-machine coordination units with host repo
+  bindings, members (`master`/`worker`/`observer`, generations), explicit assignments and a supervision graph
+  (acyclic, ≤ 6 levels) kept apart from native `parentID`. Membership and supervision grant nothing. New routes under
+  `/api/agent/workspaces…`, SDK `hub.workspaces`, 15 `workspace_*` MCP tools, and compact `workspace.*` events.
+- **Drag to supervise**: the sidebar's **Workspaces** tree shows each workspace's members under their supervisors.
+  Drag (or use Alt+arrows or the Move menu) to supervise, reorder or detach. "Spawned by" and "supervised by" are
+  shown separately.
+- **Situation board** (`GET …/board`): one bounded, text-free snapshot of members, presence, blockers, assignments,
+  Decisions and artifacts, with `stale`/`omitted`/`failed` sections instead of guesses.
+- **Supervisor digests and checkpoints**: masters and supervisors get batched, at-least-once digests as hub messages
+  from `app:workspace-coordinator`. `POST …/checkpoints` acknowledges them durably (flushed before the answer).
+- **Quieter digests**: routine updates (including snapshots) are delivered without waking an idle supervisor (2 min
+  quiet, 15 min max) and repeats of already-known states are dropped; assignment closures wake without interrupting
+  (30 s quiet, 5 min max); blockers, errors and urgent snapshots still wake and interrupt. A cleared error is still
+  reported, followed by the recovery. A member's session that disappears and comes back within one batch (a spoke
+  restart or reconnect) is not reported.
+- **Master replacement** (`POST …/master {sessionID | launchID}`): explicit, fenced, with the next generation. Supervised
+  members move to the new master. No grants move.
+
+### Panes and side chats
+- **Split panes**: **Open beside** shows up to 4 sessions or artifacts side by side, stacked or in a grid. The focused
+  pane owns the composer and Voice. Layouts are per device. On phones the panes are tabs. `/api/events` takes
+  `sessions=a,b` for the visible panes.
+- **Drag into panes**: drag a session (sidebar, Workspaces tree, Watchtower detail), an artifact (library) or a pane
+  (header grip) onto a pane: edges split side by side or stacked, the centre replaces, the layout reflows to a grid
+  when needed, and a fifth pane is refused with a notice. **Open in pane → left/right/top/bottom** in the session
+  menu is the keyboard equivalent. The layout switch is now a compact segmented control with icons.
+- **Side chats**: **Start side chat…** copies a bounded snapshot of a session into a new session on the workspace's
+  host binding (any machine), in a pane beside it, with **Refresh** and a confirmed **Send to main**. Neither
+  interrupts a running turn.
+
+### Agent profiles
+- **Shared, versioned profiles** ([docs/profiles.md](docs/profiles.md)): instructions, skills and commands (with
+  `{{param}}`, `{{arguments}}` and spoke-side `{{secret:NAME}}`), immutable versions, and import from
+  `AGENTS.md`/`CLAUDE.md`, `skills/*/SKILL.md` and `commands/*.md`. You pin an exact version to a session at runtime
+  (the profile chip), to a launch (`agentProfile`) or to a team role. The **Agent profiles** page is the library.
+  **Ctrl+Alt+P** inserts a rendered command into the composer.
+- **Per-harness application** through the new spoke feature `profileApply`, with honest acknowledgments (`applied`,
+  `partial`, `restart_required`, `unsupported`, `rejected`, `pending`): OpenCode (system prompt + `hub_profile`
+  tool), Claude Code (hook context, `set_model` in launched sessions), Codex (developer message + skill files);
+  presets are always `unsupported`. Local instructions win. No global harness config is written.
+- **Profile metadata and usage**: optional `metadata` and `projects` on a profile, and **Used by**
+  (`GET /api/agent/profiles/:id/usage`, SDK `hub.profiles.usage()`, MCP `profile_usage`): pinned sessions with
+  requested vs running version and an explicit Upgrade, team roles, launches and workspaces, each shown only under the
+  caller's existing read rules (`hidden` names what was left out). The library rows show usage chips, with filters and
+  sort.
+
+### Artifacts and AI
+- **Persistent artifacts** ([docs/artifacts.md](docs/artifacts.md)): revisions of content-addressed blobs (files
+  standalone, chunked Postgres in a cluster), `private` or `workspace` visibility, archive and delete, staged uploads up
+  to 25 MiB, and downloads always served as attachments. New routes, SDK `hub.artifacts`, and `artifact_*` MCP tools.
+- **Viewers and dashboards**: markdown, code, images, tables, charts, and declarative dashboards (schema v1, bindings
+  to other artifacts only, no URLs or scripts), plus a text editor with conflict-safe drafts.
+- **AI jobs**: ask, propose an edit or run a declared action. The job runs on a handler you choose (a new launch or an
+  existing session), always with the requester's authority. Proposals apply only when you **Accept**. Jobs survive hub
+  restarts, and each job times out after 2 h.
+- **Viewer redesign**: a header bar with kind icon, version picker (**Back to latest**), Copy, Download, Edit, Open in
+  pane and a details popover; content in a framed card (code with file/language header, line numbers, wrap; markdown
+  at reading width; dashboards and apps full-bleed); inline editing; and AI as a chat-style side panel (thread,
+  composer, Ask / Edit / Action or slash commands, compact handler picker that never preselects), resizable, a
+  bottom sheet on phones.
+
+### Isolated artifact host
+- Interactive `html`/`app` artifacts run only at `/artifact-host/v1/<capability>/…`: an opaque-origin sandbox with a
+  strict CSP, short-lived, viewer-bound and revocable capabilities, and a bridge (`resize`, `askAI`). Every `askAI`
+  becomes a consent card in the artifact's AI panel thread ([docs/artifact-host.md](docs/artifact-host.md)).
+
+### Teams
+- **Teams** ([docs/teams.md](docs/teams.md)): versioned definitions with roles, one entry role, `open` or `restricted`
+  communication paths (`one-way`/`two-way`, `msg`/`ask`), and a draft → publish flow. A session can belong to many
+  teams. The hub **enforces** the policy on delivery (`403 forbidden` with `extra.policy`). Team members cannot contact
+  sessions outside their teams unless a role has `externalContact`. Sessions in no team are unchanged.
+- **Staffing** with existing or newly launched sessions under your grants (`403 needs_user` lists what is missing).
+  **Intake** gives work to the team's entry role and tracks it as an assignment ([docs/teams-intake.md](docs/teams-intake.md)).
+- **Team addresses** `@@role#team` and `@@role.project#team` (quote `#` in shells). `/who`, `status` and `show` are
+  team-aware for team members.
+- Malformed addresses answer `Not an address: use ses_…, @name, @@role or @@role#team` with a syntax-only hint (for
+  `@engineer#support`: `@@engineer#support` or `@engineer`); the hint never reveals whether a name exists.
+- Entry-role sessions report and close their intake from the harness: OpenCode `hub` tool verbs `intake` and
+  `intake_update`, MCP `team_intake_update` (`expectedRevision` now optional). The intake message says how.
+- **Teams page** (`/teams`, in the primary navigation): team cards (mode, entry role, seats, vacant roles, open work),
+  **New team** in a dialog, and per team **Members** (one block per role, **+ Add member** with a searchable session
+  picker that shows other memberships, **Launch new …**), **Work** (Submit a task, live intake status with links to
+  the entry session and its assignment), **Communication** and **Details** (draft → Review and publish, history),
+  Pause/Archive and **Edit in Watchtower**. The Watchtower's team panel uses the same components and links back.
+- **Team isolation** (owner setting, default off): Settings → Teams, or `GET/PUT /api/agent/team-settings`
+  `{teamIsolation, expectedRevision}` (users only; SDK `hub.teams.settings()` / `setSettings()`). On: team members
+  see only their teams' sessions.
+
+### Watchtower
+- Renamed from **Bird's-eye view** (new lookout icon). `/birds-eye` links redirect to `/watchtower` with their
+  filters, and the browser's saved view and presets (`birdsEye.*`) move to `watchtower.*` once.
+- A full-screen page ([docs/watchtower.md](docs/watchtower.md)) of machines, sessions, you, your apps and teams, with
+  live message flow: 3D (lazy `3d-force-graph`), a deterministic 2D canvas, or a list (also used for reduced motion).
+  It has URL-state filters and presets, team clusters, drawn vs actual paths and denied attempts, and a **team
+  editor** to assemble, staff, publish and submit work. New read API `GET /api/agent/graph` (+ `/edges/:id`,
+  `/nodes/:id`).
+- Graph first: the controls are a floating **dock** at the bottom centre (view, Filters with an active count, Legend,
+  Teams, Hub details, Reset view, Pause motion, Search) that fades when idle. **Filters** is closed by default and
+  shows only the filters you add; active filters are removable chips over the canvas. The **Legend** has a visible
+  close and Escape closes it. On phones, filters, legend, details and the team editor are bottom sheets.
+- A look in the style of Brain Graph (MIT, credited in the docs): glowing points in coloured group regions, fibers that
+  brighten towards the receiver, depth of field, labels on the most connected nodes, and a stable layout kept per
+  device (`watchtower.layout`). Flow pulses fade with message age and stop once nothing on a link is working or
+  pending. Rendering is on demand (none while still or hidden), and the 3D view draws in about 25 batched calls.
+- Staffed seats are tied to their role by a tether and vacant roles are drawn hollow; the legend uses the same glyphs;
+  **More → Re-layout** clears the saved layout; the empty state sits below the hub core with **Connect a machine**.
+
+### Navigation
+- A primary navigation above the session groups: **All sessions**, **Artifacts** (a library across workspaces),
+  **Watchtower** and **Agent profiles**.
+- **Settings sections**: General, Notifications, Voice & speech, Machines & devices, Agents & access, Teams and Admin,
+  each its own page `/settings/<section>` (deep links, back/forward; old `/settings#speech`-style links still work).
+  A section sidebar on desktop, a section list with drill-in on phones, and a **Search settings** box that jumps to a
+  setting and highlights it. Notification kinds are collapsed by group with an on/off summary; the device's push
+  status is one line with **Details**.
+
+### Security hardening
+- **Bounded request bodies** everywhere: agent JSON 1 MiB, profiles 4 MiB, console JSON 4 MiB, `/mcp` 1 MiB, staged
+  blobs 25 MiB, all read by a rate-budgeted streaming reader. Oversized bodies are refused with `Connection: close`.
+  **Set a front-proxy request-body limit (26 MiB)**: the k8s ingress example now uses `proxy-body-size: 26m` (it was
+  `16m`).
+- A session seated in a team no longer sees sessions seated only in *other* teams: they are left out of `who`,
+  `status`, `show`, `log`, `/watch` and `/events`, and their addresses answer `404` like unknown ones. Sessions in no
+  team stay visible unless the owner turns on `teamIsolation` (Settings → Teams). Users, apps and team-less sessions
+  keep the owner-wide view.
+- New app-token scopes `workspaces:*`, `profiles:*`, `artifacts:*` and `teams:*`. **Existing tokens gain nothing**,
+  and session tokens are refused on workspace routes.
+- **Plain http only by opt-in**: `hub login` (device code, `--token` or a piped token) and `hub`/`hubctl machine enroll`
+  refuse plain http except on loopback, or with `--allow-insecure-http` for a private-network IP address (never a
+  host name), with a warning every time; nothing remembers the flag, and later commands using a stored plain-http
+  login warn on stderr. A loopback hub's approval link on this machine's LAN address is shown; other origins are
+  replaced with a warning.
+
+### Fixes
+- Counts pluralise correctly ("2 OpenCode processes", not "processs"); a team role's seat counter reads "1 of 2
+  required", "3 members · up to 16" or "full (16)" instead of "1 of 0–16".
+- The artifact AI panel lists handler sessions by `@name` (searchable by name, title or ID) and names a handler picked
+  in the console by its `@name` instead of its session ID.
+- The console's live stream opens at once when it resumes (the hub writes a first chunk immediately); before, it waited
+  for the 20 s heartbeat and **Reconnecting…** stayed up, across pages. Over plain http, Chrome still allows only 6
+  connections per host, so more than about 6 console tabs stall; https avoids this.
+- The sidebar, Details rail and pane resize handles show their resize pointer again (a hidden character had broken
+  those CSS rules).
+- `hub node` keeps OpenCode's background service warm (loopback only, every 30 s) so a freshly started service's
+  machine comes online without anyone opening a project (OpenCode has no server-start plugin hook).
+- **Routine `wake: false` messages no longer cost an OpenCode session a turn** (routine digests, `--no-wake`
+  messages). OpenCode gives every queued inbox item its own model call once a turn ends, resume or not, so a
+  supervisor answered each routine digest in a turn of its own. The OpenCode spoke now admits every non-waking
+  message steered without resume, and refuses a routine one (a `wake: false` `msg` that is not urgent, to a top-level
+  session) while a turn runs: the hub keeps it `pending` and delivers it after the turn, so it reaches the model with
+  the next real turn, before its prompt (CLI and MCP say "pending (offline or busy; …)"). A waking message to the
+  same session sends the pending ones first (if the session is still busy, the waking one goes first, queued after
+  the turn). A flush stops at a session's first failed delivery, so a busy session costs one try per sessions frame.
+  Urgent
+  ones, asks, replies, primers and anything for a subagent still go into a running turn. Live check:
+  `HUB_IT_OPENCODE=1 bun test test/e2e-quiet-delivery.it.test.ts`.
+- **Repeated blocks of one member no longer wake its supervisor each time**: blocked again for the same reason (same
+  blocker kind, or the same blocked/error state) within 15 min of a wake about it that the hub carried out, the
+  digest line is routine.
+- **A run that fails at once shows as failed** (a model or provider that does not exist, auth, quota). OpenCode ends
+  such a run within ~50 ms of `session.created`, before the spoke's debounced sessions snapshot (500 ms), and the hub
+  keeps status only for sessions it was told about, so it dropped the failure and listed the session idle: no banner,
+  no "!" badge, not under Needs you, no `providerError` push (also in 0.7.3). The spoke now sends the snapshot first
+  when a run event is about a session the hub has not been told about yet (creating sessions alone still waits for the
+  debounce), and resends a failure once a snapshot lists its session if the session's details were still being
+  fetched when it failed. Live check: `HUB_IT_OPENCODE=1 bun test test/spoke-run-failure.it.test.ts`.
+- **A session is never routed to another harness's spoke.** When no process owns a session and none of its
+  reporters is a service, the hub falls back to a background service on the reporter's machine; it took any service,
+  so an OpenCode session reported by a foreground `opencode serve` on a machine that also runs the Claude Code (or
+  Codex) service went to that service: "The claude-code spoke does not serve "timeline"" and `unsupported: summary`
+  (also in 0.7.3). The fallback now takes only a service of the session's own harness, else the reporter itself.
+
+### Runtime
+- **Bun 1.4.4**, pinned: the image (`oven/bun:1.4.4-slim` by digest, both stages), CI and release workflows, and
+  `engines.bun` (`>=1.4.4`). Bun 1.3.x's `Bun.SQL` auto-pipelining could stall a pooled Postgres connection under
+  concurrent writes (oven-sh/bun#33985; fixed in Bun 1.4.0 by oven-sh/bun#33627): a cluster pod's state queries then
+  never answered (the supervision IT's "many concurrent internal moves" hung or timed out in 3 of 15 runs on 1.3.5,
+  0 of 40 on 1.4.4).
+- Cluster: the Postgres pools set `statement_timeout` (30 s by default, `HUB_DATABASE_STATEMENT_TIMEOUT_MS`, `0`
+  off), so a query stuck on the database fails with an error instead of holding its caller and connection.
+- Bun 1.4 enforces the server's request ceiling on chunked bodies too; the ceiling now leaves 16 MiB above the
+  largest route bound, so an over-limit upload still gets the route's own `400`/`413` with `Connection: close`. Bun
+  1.4 then closes the socket instead of reading and discarding whatever the client keeps sending.
+- The image build copies the protocol and SDK sources into the console stage, which imports them (without them
+  `docker build` failed in the console's `vite build`).
+
+### Behavior notes
+- New agent error code `conflict` (409, with `currentRevision`) for stale `expectedRevision`s and reused
+  `Idempotency-Key`s. The SDK `ErrorCode` includes it, and the CLI exits 3.
+- The server's request ceiling rises from about 10 MiB to about 41 MiB (25 MiB blobs plus drain headroom). A JSON body
+  that was accepted before can now be refused as too large (by its route's bound).
+- SDK `parseAddress` refuses `#` in a role's project scope (`@@role#team` is only ever team-resolved).
+- Send to main and AI jobs handled by a session use normal delivery: they never interrupt a running turn. The first
+  message to an idle session right after the hub's primer may be delivered as steer.
+- Cluster: schema v2 (`artifact-blobs`). Run `hub-server migrate` before rolling pods, and don't create restricted
+  teams while old and new pods are mixed.
+
+## 0.7.4
+
+Release downloads move to a public repository. The source repository is private now, so the standalone `hub`
+binaries, `hubctl`, its signed manifest and the checksums are published to
+[`huynle/hub-releases`](https://github.com/huynle/hub-releases) (the release workflow mirrors every release there,
+byte for byte, so the signed manifest and checksums stay valid). The image `ghcr.io/huynle/hub` and the npm package
+`@huynle/hub` are unchanged.
+
+- **Install**: the README, the Ansible role README and the web shell hint use `huynle/hub-releases`; pass
+  `--release-url https://github.com/huynle/hub-releases/releases/download/v<version>` to `hubctl setup ansible`.
+- **Plugin rename notice** no longer suggests installing from `github:huynle/hub`.
+
 ## 0.7.3
 
 Session errors are visible: a quota, auth or rate-limit error in an OpenCode session now shows up in the hub.

package/Dockerfile

@@ -7,6 +7,8 @@
 # Legacy VOICE_* variables still work, except that the HUB_HOST/HUB_PORT/HUB_STATE_DIR defaults below
 # win over VOICE_HOST/VOICE_PORT/VOICE_STATE_DIR: rename those overrides to HUB_*.
 # The console (web/, Solid + Vite) is built in its own stage; the image ships only web/dist.
+# Bun is pinned (tag and multi-arch index digest) to 1.4.4: it has the Bun.SQL pipelining fix (oven-sh/bun#33627,
+# in since 1.4.0; 1.3.x stalls pooled Postgres connections in cluster mode). Bump both stages together.
 FROM node:22-slim AS web
 WORKDIR /build
 COPY package.json package-lock.json ./
@@ -24,9 +26,12 @@ COPY packages/preset/package.json ./packages/preset/
 COPY packages/codex/package.json ./packages/codex/
 RUN npm ci --no-audit --no-fund --ignore-scripts
 COPY web ./web
+# The console imports the protocol and SDK sources (web/src/… ../packages/{protocol,sdk}/src).
+COPY packages/protocol/src ./packages/protocol/src
+COPY packages/sdk/src ./packages/sdk/src
 RUN npx vite build --config web/vite.config.ts
 
-FROM oven/bun:1.3-slim AS deps
+FROM oven/bun:1.4.4-slim@sha256:1846adf22496bd711036aae8be147e57bdebbaea2e5264e3e0b5af1db187d9a4 AS deps
 WORKDIR /build
 COPY package.json package-lock.json ./
 COPY packages/protocol/package.json ./packages/protocol/
@@ -47,7 +52,7 @@ COPY docker/hub-deps.ts ./
 # Keep only what the hub loads at runtime (the @opencode/* packages are for the plugin).
 RUN bun hub-deps.ts /deps web-push
 
-FROM oven/bun:1.3-slim
+FROM oven/bun:1.4.4-slim@sha256:1846adf22496bd711036aae8be147e57bdebbaea2e5264e3e0b5af1db187d9a4
 LABEL org.opencontainers.image.title="hub" \
       org.opencontainers.image.description="Hub: a central hub for AI agent harnesses (OpenCode first): remote console, pairing, push and optional Voice" \
       org.opencontainers.image.licenses="MIT" \