@tt-a1i/hive 2.1.0 → 2.1.3

package/CHANGELOG.md

@@ -2,6 +2,46 @@
 
 All notable user-facing changes will be documented in this file.
 
+## 2.1.3 - 2026-06-18
+
+Issue backlog polish for onboarding, dispatch, demo, and release readiness.
+
+- Holds Hive startup instruction injection while first-run CLI setup prompts are
+  visible, avoiding collisions with trust/login/confirmation onboarding screens.
+- Adds a first-dispatch guide on the Orchestrator pane for non-scenario flows,
+  and makes user-input delivery truthful when the Orchestrator PTY is offline.
+- Adds language-aware built-in role contracts and scenario/spawn defaults so
+  English workspaces no longer receive zh-only worker prompts.
+- Replaces the external demo video with a local self-running Hive replay that
+  shows task progress, worker states, and team dispatch flow.
+- Adds a local CLI compatibility report for native modules and Tier-1 agent
+  CLIs, wired into release verification.
+- Surfaces local-only retention diagnostics in Settings and adds candidate
+  memory review controls to the Memory drawer.
+- Re-verifies the existing `team recall` route, CLI, and remote relay path.
+
+## 2.1.2 - 2026-06-16
+
+Spawned-worker dispatch reliability.
+
+- Fixes `team spawn` followed by `team send`: newly spawned workers now wake for
+  their first task instead of leaving the dispatch parked in the stopped queue.
+- Keeps stopped-worker semantics intact after that first run: if a spawned
+  worker is later stopped manually, new sends stay queued until the worker is
+  started again.
+- Makes Windows Claude Code sessions more tolerant of large Hive startup and
+  dispatch injections, reducing premature submit/input residue during agent
+  startup.
+
+## 2.1.1 - 2026-06-14
+
+Codex terminal input polish and Action Center mobile refinements.
+
+- Makes Codex terminal input smoother and more reliable during pasted or
+  programmatically injected prompts.
+- Polishes the Action Center layout and interaction details, especially on
+  narrower and mobile-sized screens.
+
 ## 2.1.0 - 2026-06-13
 
 Sentinel patrol role, one-click team assembly, visible memory consolidation, and remote/dispatch reliability.

package/README.en.md

@@ -1,464 +1,9 @@
-<p align="center">
-  <img src="./assets/logo.png" width="120" alt="Hive logo" />
-</p>
+# Hive English README
 
-# Hive
+The English README is now the default GitHub entry point:
 
-<p align="center">
-  <img src="./assets/hive-hero.png" alt="Hive local-first multi-agent collaboration workspace hero image" />
-</p>
+[README.md](./README.md)
 
-**Hive is a browser-native workbench where a team of agents works together — one orchestrates, the rest execute, all on your laptop.** The orchestrator
-is a real `agy` / `claude` / `codex` / `opencode` / `gemini` / `hermes` / `qwen` process — not you, and
-not a script — and so are the workers it dispatches to. Every agent runs as
-a real PTY on your machine, talks through a small `team` protocol that Hive
-injects into each agent's shell, and shares a markdown task graph at
-`<workspace>/.hive/tasks.md`.
+Chinese documentation is available here:
 
-Code, research, drafts, translations — if a team can split the work, a hive can take it on.
-
-[![npm](https://img.shields.io/npm/v/@tt-a1i/hive.svg)](https://www.npmjs.com/package/@tt-a1i/hive)
-[![ci](https://img.shields.io/github/actions/workflow/status/tt-a1i/hive/release.yml?branch=main&label=ci)](https://github.com/tt-a1i/hive/actions/workflows/release.yml)
-[![Website](https://img.shields.io/badge/website-hivehq.dev-5a8a8a.svg)](https://hivehq.dev)
-[![Node](https://img.shields.io/badge/node-%3E%3D22-3c873a.svg)](https://nodejs.org/)
-[![License](https://img.shields.io/badge/license-BUSL--1.1-orange.svg)](./LICENSE.BSL)
-[![Platforms](https://img.shields.io/badge/platforms-macOS%20%C2%B7%20Linux%20%C2%B7%20Windows%20(best--effort)-lightgrey.svg)](#platform-support)
-
-🌐 **Website**: [hivehq.dev/en/](https://hivehq.dev/en/) · [中文](https://hivehq.dev/)
-
-English · [简体中文](./README.md)
-
-> Hive is local-first, runs on `127.0.0.1`, and is intended for anyone who
-> already runs CLI agents. The latest stable release is on
-> [npm](https://www.npmjs.com/package/@tt-a1i/hive) and the badge above resolves
-> to it.
-
-<p align="center">
-  <img src="./assets/hive-team-view.png" alt="Hive workbench with a 4-agent team — orchestrator dispatching while workers run" />
-</p>
-
-## Why Hive
-
-CLI agents are powerful, but coordinating several of them manually is
-awkward:
-
-- Long-running sessions are spread across terminals.
-- Splitting work across agents — implementation/review/testing,
-  research/drafting/fact-checking, or any other division of labor — needs a
-  routing layer you don't have.
-- Worker progress disappears into scrollback.
-- Restart recovery depends on each CLI's native session behavior.
-
-Hive adds the coordination layer without replacing the CLIs. Agents stay as
-real terminal processes on your machine; Hive just manages the shell around
-them.
-
-## Try the demo first
-
-Don't have an agent CLI installed yet? Run `hive`, open the printed URL, and
-click **Try Demo** in the first-run wizard. The current demo is a walkthrough
-video hosted on Bilibili (network access required to play it) plus a sample
-team in the sidebar, so you can see the orchestrator dispatching and workers
-reporting without installing or signing in to any real CLI agent. Useful for
-deciding whether to install a real CLI.
-
-## Quick Start
-
-Prerequisites:
-
-- Node.js 22 or newer.
-- At least one supported agent CLI installed, authenticated, and available on
-  `PATH`.
-
-Install and start Hive:
-
-```bash
-npm install -g @tt-a1i/hive
-hive
-```
-
-If npm prints `npm warn allow-scripts` or `prebuild-install@7.1.3 deprecated`
-during install, first check whether the command ends with `added ... packages`.
-Those warnings usually come from npm's install-script review plus native
-binary setup for `node-pty`, `better-sqlite3`, and `esbuild`; they do not mean
-Hive failed to install. The troubleshooting section below breaks them down.
-
-Open the printed local URL, usually `http://127.0.0.1:3000/`. Use
-`hive --port 4010` when you need a specific local port.
-
-To upgrade in place:
-
-```bash
-hive update
-```
-
-`hive update` runs `npm install -g @tt-a1i/hive@latest` in place. Restart any
-in-flight Hive process to pick up the new version. If you installed Hive with
-pnpm or yarn, upgrade through the same package manager — otherwise the new
-npm copy will shadow your existing install.
-
-Install Hive as an app (optional):
-
-Open `http://127.0.0.1:3000/` in Chrome, Edge, or Brave and click the install
-icon at the right edge of the browser's omnibox. The PWA launches in its own
-dock-anchored window without browser chrome and shows **Add Workspace** /
-**Try Demo** shortcuts from the dock right-click menu. Firefox and Safari
-currently don't implement the install-prompt protocol, so the omnibox icon
-only appears in Chromium-based browsers.
-
-The Hive daemon must still be running for the PWA to do anything; if the
-runtime isn't reachable when you launch the app, you'll see a "Hive runtime
-is not running" page that auto-reloads once `hive` is back on `127.0.0.1`.
-The PWA install scope is keyed by origin, so `hive --port 4011` installs as
-a separate app from `hive --port 3000`. To uninstall, visit `chrome://apps`,
-right-click the Hive tile, and choose **Remove from Chrome…**.
-
-Hive asks the browser to confirm before closing the tab or PWA window so an
-accidental close shortcut (Cmd-W on macOS, Ctrl-W on Windows/Linux) doesn't
-drop your session. Modern browsers gate that prompt on prior page interaction
-— if you open the PWA and immediately press the close shortcut without
-clicking or typing anywhere first, it still closes cleanly. That's a browser
-policy, not a Hive bug.
-
-First-run flow:
-
-1. Create a workspace from a project folder.
-2. Choose an Orchestrator preset.
-3. Hive creates `<workspace>/.hive/tasks.md`, starts the Orchestrator PTY, and
-   injects the internal `team` command into the agent session.
-4. Add workers from the Team Members panel.
-5. Ask the Orchestrator to delegate work. It sends tasks with
-   `team send <worker-name> "<task>"`; workers report back with `team report`.
-
-If you want the Orchestrator to size the team itself, leave **Auto-staff**
-enabled (it is on by default). It can `team spawn` the right temporary mix of
-coders, testers, and reviewers for the task, then Hive dismisses those
-temporary workers when their work is done.
-
-For stronger automation, enable the experimental **Workflows** toggle in
-settings. The Orchestrator can then author and run multi-agent workflows that
-fan out across implementation, review, testing, or other stages. The topbar
-**Workflows** panel shows runs, phase results, logs, schedules, and stop
-controls. The same panel also lets you choose which CLI workflow-created
-agents use by default and which CLIs they are allowed to use.
-
-## How It Works
-
-```text
-Browser UI on 127.0.0.1
-  tasks, team, terminals, reports
-          |
-          | HTTP + WebSocket
-          v
-Hive runtime
-  SQLite metadata, PTY lifecycle, task dispatch
-          |
-          +-- Orchestrator PTY
-          |     can call: team send, team list, team report
-          |
-          +-- Worker PTY
-          |     can call: team report
-          |
-          +-- Worker PTY
-                can call: team report
-
-Workspace task graph:
-  <workspace>/.hive/tasks.md
-```
-
-Three details matter:
-
-- Agents are real CLI processes, not simulated subagents.
-- `team` is injected only inside Hive-managed agent sessions by prepending the
-  package's internal bin directory to `PATH`; it is not installed as a global
-  command.
-- The task graph is a markdown file in the workspace, so you can inspect or
-  edit it outside the app.
-
-## Agent Presets
-
-| Preset | Command expected on `PATH` | Default bypass mode | Session resume |
-| --- | --- | --- | --- |
-| Antigravity CLI | `agy` | `--dangerously-skip-permissions` | `--conversation <session_id>` |
-| Claude Code | `claude` | `--dangerously-skip-permissions`, `--permission-mode=bypassPermissions` | `--resume <session_id>` |
-| Codex | `codex` | `--dangerously-bypass-approvals-and-sandbox` | `resume <session_id>` |
-| OpenCode | `opencode` | Config-driven in `~/.config/opencode/opencode.json` | `--session <session_id>` |
-| Gemini | `gemini` | `--yolo` | `--resume <session_id>` |
-| Hermes | `hermes` | `--yolo` | `--resume <session_id>` |
-| Qwen Code | `qwen` | `--approval-mode yolo` | `--resume <session_id>` |
-| Cursor CLI | `cursor` | `--force` | Session id capture not wired yet |
-| Grok Build | `grok` | `--always-approve` | Session id capture not wired yet |
-| Custom | Any executable | User configured | User configured |
-
-Hive does not install these CLIs for you. Install and authenticate them in the
-same shell environment you use to start Hive.
-
-## What Hive Provides
-
-- Workspace sidebar for switching between local projects.
-- Orchestrator and worker terminals backed by real PTYs.
-- Add Worker flow with role presets for coder, reviewer, tester, and fully
-  custom prompts and commands — wire any CLI agent into the role you need.
-- Auto-staff (experimental, on by default): the Orchestrator can create
-  temporary coders, testers, and reviewers based on the task, and Hive cleans
-  them up after their dispatch reports back.
-- Workflows (experimental, off by default): the Orchestrator can run
-  multi-stage, multi-agent workflows while Hive shows runs, logs, results,
-  schedules, and stop controls in the Workflows panel.
-- Workflow CLI policy: choose the default CLI for workflow-created agents and
-  restrict which CLIs workflow scripts may launch.
-- `.hive/tasks.md` editor with external-file conflict handling.
-- Background PTY preservation and best-effort native session resume.
-- A What's New dialog after upgrades with curated release highlights.
-- Local SQLite metadata under `%APPDATA%\hive` on Windows and `~/.config/hive`
-  on macOS / Linux by default, or `$HIVE_DATA_DIR` when set.
-
-Hive does not provide sandboxing, multi-user auth, or any bundled agent
-model. It coordinates the CLIs you already run locally.
-
-## Remote Access (optional, off by default)
-
-If you want to reach your running Hive from your phone while you're away,
-turn on the optional **Remote access** feature. Once enabled, a phone browser
-logs in at a gateway with GitHub or Google, pairs once with the desktop, and
-then reaches the **full** Hive web UI over an end-to-end encrypted tunnel — a
-paired phone is a trusted device with the **same authority** as the local
-browser.
-
-A few things to be clear about:
-
-- **Off by default.** With it off there are no outbound connections and
-  nothing listening — behavior is exactly what it is today.
-- **Requires a gateway.** The tunnel is relayed through a gateway (your
-  local daemon dials out to it — no open ports, no router changes). The
-  gateway URL is configurable: **self-host** a Cloudflare Workers gateway,
-  or point at one that's already deployed. There is **no turnkey hosted
-  service** — you stand the gateway up yourself.
-- **Data and execution stay local.** The gateway only does identity (OAuth
-  login) and routing; it never sees plaintext, only relays ciphertext. If the
-  gateway is down, everything on local `127.0.0.1` keeps working.
-- **End-to-end encrypted.** Every data frame between the phone and the daemon
-  is end-to-end encrypted; the gateway sees only ciphertext and routing
-  headers. The honest caveat: the phone's crypto code is served by the gateway
-  (the classic limit of web-delivered E2E, like Proton or WhatsApp Web),
-  mitigated by SRI, versioned bundles, and PWA caching that forms a TOFU
-  baseline. We don't claim "secure even if the gateway is compromised."
-- **Trust root stays on the desktop.** Pairing a new device must be confirmed
-  in person at the computer (a desktop dialog plus a 6-digit SAS check); a
-  paired phone can't approve new devices on its own. Devices can be revoked at
-  any time.
-
-See [docs/remote-access.md](docs/remote-access.md) for the full enable,
-login (`hive remote login`), pairing, revoke, and self-host-gateway walkthrough.
-
-## Platform Support
-
-| Platform | Status | Notes |
-| --- | --- | --- |
-| macOS | Tier 1 | Main development and release verification target. |
-| Linux | Tier 1 | CI verified. Native folder picking expects `zenity`; manual path entry works without it. |
-| Windows | Tier 2 | CI runs a Windows test subset and a packaged-install smoke. Workspace selection uses Hive's in-browser server filesystem picker by default, starting at "This PC" so other drives are visible; the package includes `team.cmd`. Treat as best-effort — full Windows verification before each release is manual. |
-
-All platforms require Node.js 22+. Hive depends on native packages
-(`node-pty` and `better-sqlite3`), so native install tooling may be required
-when prebuilt binaries are unavailable.
-
-## Safety Model
-
-Hive is a local development tool, not a hosted service.
-
-- The runtime binds to `127.0.0.1`. Do not expose the Hive port through a public
-  tunnel, reverse proxy, or shared network interface.
-- Built-in presets intentionally use each CLI's non-interactive or bypass mode
-  where available. Treat workers as able to run arbitrary shell commands inside
-  the selected workspace.
-- Open only trusted workspaces. A worker has the same filesystem access as the
-  shell account running Hive.
-- Agent tokens are session scoped, generated by the local runtime, injected into
-  agent process environments, and not intended as internet-facing credentials.
-- Hive has no multi-user authentication boundary. Treat same-machine processes
-  that can reach the local port as trusted local access.
-- The browser UI token is a local session guard, not protection against other
-  processes already running as your OS user.
-
-Read [SECURITY.md](SECURITY.md) before using Hive with sensitive repositories.
-
-## Data Locations
-
-| Data | Location |
-| --- | --- |
-| Runtime metadata | Windows: `%APPDATA%\hive`; macOS / Linux: `~/.config/hive`; or `$HIVE_DATA_DIR` |
-| Workspace tasks | `<workspace>/.hive/tasks.md` |
-| Internal `team` command | Packaged under `dist/bin/`, injected into PTYs |
-| Web UI assets | Served by the runtime from the packaged `web/dist` build |
-
-## Troubleshooting
-
-**Agent CLI not found**
-
-Check that the selected command is installed, authenticated, executable from the
-same shell, and available on `PATH`.
-
-**Port already in use**
-
-Start Hive with another local port:
-
-```bash
-hive --port 4020
-```
-
-**Native package install fails**
-
-Hive depends on `node-pty` and `better-sqlite3`, which use native binaries. Use
-Node.js 22+, keep your package manager cache clean, and verify your platform
-build tools are available.
-
-When install succeeds but npm prints warnings, read them by source:
-
-| warning | Source | What to do |
-| --- | --- | --- |
-| `allow-scripts @tt-a1i/hive` | Hive's postinstall fixes executable bits for packaged native / PTY helpers. | Safe to ignore after a successful install. |
-| `allow-scripts better-sqlite3` | SQLite native bindings download a prebuilt binary, then fall back to local build. | Safe to ignore after success; check build tools only if install fails. |
-| `allow-scripts node-pty` | The terminal PTY binding prepares platform binaries. | Safe to ignore after success; check build tools only if install fails. |
-| `allow-scripts esbuild` | esbuild verifies/selects the binary package for the current platform. | Safe to ignore after a successful install. |
-
-This is npm 11's install-script review notice. The current npm release still
-treats it as advisory; future npm versions may require explicit approval. To
-review the list yourself, run `npm approve-scripts --allow-scripts-pending`.
-
-If npm prints a deprecated warning for `prebuild-install@7.1.3`, it is safe to
-ignore. The warning comes from `better-sqlite3`'s native binary download chain;
-it is an upstream installer maintenance notice, not a Hive install failure, and
-does not affect runtime behavior.
-
-**Folder picker does not open on Linux**
-
-Install `zenity`, or paste the workspace path manually.
-
-**Folder picker on Windows**
-
-Hive uses the in-browser server filesystem browser by default on Windows
-instead of launching the PowerShell native folder picker. This avoids the
-system dialog getting hidden behind the browser window. The browser starts at
-"This PC" and lists accessible drives, so `C:\`, `D:\`, and other drives are
-reachable. If the target directory is not visible in the browser list, expand
-"Advanced: paste path" and enter the absolute path directly.
-
-**Tasks file conflict banner appears**
-
-Hive detected a newer `.hive/tasks.md` on disk. Use `Reload` to accept the file
-from disk, or `Keep Local` to keep the editor contents and save again.
-
-**Worker appears stuck in `working`**
-
-Hive does not guess task completion from process activity. Workers move back to
-`idle` when they call `team report`. If a worker is blocked, stop or restart it
-from the UI.
-
-## Development
-
-```bash
-pnpm install
-pnpm dev
-```
-
-Development mode runs the runtime on `127.0.0.1:4010`; Vite runs on
-`127.0.0.1:5180` and proxies API and WebSocket traffic to the runtime.
-
-Useful checks:
-
-```bash
-pnpm check
-pnpm build
-pnpm test
-```
-
-Production-style local run:
-
-```bash
-pnpm build
-node dist/src/cli/hive.js --port 4010
-```
-
-The production server serves the built web UI directly. No Vite server is
-needed after `pnpm build`.
-
-## Release
-
-Maintainer dry run:
-
-```bash
-pnpm release:dry
-```
-
-See [docs/release.md](docs/release.md) for the full tagged release checklist,
-including manual Windows smoke steps.
-
-Tag pushes matching `v*` run the GitHub Actions release workflow. The workflow
-verifies macOS, Ubuntu, and Windows, then publishes to npm with `NPM_TOKEN`.
-
-## Status
-
-Hive is in alpha. The core flow is usable today; current work focuses on
-polishing the multi-agent collaboration workflow, Windows support, and clearer
-orchestration observability. Try it out and open issues — feedback shapes what
-gets prioritized next.
-
-## On the roadmap: cross-agent long-term memory
-
-<p align="center">
-  <a href="https://github.com/EverMind-AI/EverOS">
-    <img src="https://avatars.githubusercontent.com/EverMind-AI" width="72" alt="EverMind / EverOS" />
-  </a>
-</p>
-
-Single-agent memory already exists, but the styles diverge:
-
-- **Claude Code's [Auto Dream](https://claudefa.st/blog/guide/mechanics/auto-dream)** is **batch / offline** — invoked via `/dream` (or on a 24h timer), Claude consolidates JSONL session logs in the cloud, merges duplicates, extracts patterns, and proposes a new memory file for you to review and adopt. REM-sleep style, with a clean wake/sleep separation.
-- **Hermes Agent** runs the opposite playbook — **embedded and in-stride**. Every N turns it forks a background sub-agent to review the recent exchange and writes directly into a **multi-organ local store**: `MEMORY.md` (facts/rules) · `USER.md` (who-you-are) · SQLite + FTS5 (episodic search) · Honcho (third-person model) · `skills/` (procedural memory). The agent is allowed to edit its own skill files in stride — memory and capability are the same thing.
-
-But these are all **per-agent** memories. Hive coordinates *teams* of agents, so the next step is wiring them together: let the whole team **share one long-term memory store** — what Worker A learned today becomes context the Orchestrator can dispatch to Worker B tomorrow.
-
-We're planning to back this with **[EverOS](https://github.com/EverMind-AI/EverOS)**
-— an open-source long-term memory OS from [EverMind](https://evermind.ai/),
-currently SOTA on the LoCoMo / LongMemEval / HaluMem memory benchmarks.
-Its four-layer architecture (Agentic / Memory / Index / API+MCP) maps
-cleanly onto Hive's multi-PTY model: each agent keeps its in-CLI memory,
-team-level facts flow through EverOS, and the Orchestrator joins both
-when dispatching.
-
-Track progress at [#6](https://github.com/tt-a1i/hive/issues/6) — drop a
-+1 or comment with your use case to influence priority.
-
-## A different form factor: squad
-
-If you'd rather have **pure CLI, zero background process, and the ability to
-run on a remote SSH box**, [squad](https://github.com/mco-org/squad) takes the
-same idea down a different path — SQLite as the protocol layer, one terminal
-per agent. The two projects don't replace each other; pick by workflow:
-
-- **Hive** — visual workbench, one-click restart, workspace sidebar, easier to demo to a team
-- **squad** — lives in tmux, SSH remote dev, no extra background process, Windows servers
-
-## Acknowledgements
-
-The built-in template marketplace ships snapshots of two community-maintained prompt libraries, both distributed under their upstream MIT licenses:
-
-- English (used when the UI is set to EN): [`msitarzewski/agency-agents`](https://github.com/msitarzewski/agency-agents)
-- Chinese (used when the UI is set to 中文): [`jnMetaCode/agency-agents-zh`](https://github.com/jnMetaCode/agency-agents-zh)
-
-Upstream content is mirrored verbatim, license files are kept under `vendor/marketplace/<lang>/LICENSE`, and snapshots are refreshed by `pnpm sync:marketplace` before each Hive release.
-
-## License
-
-Hive is **source-available under the Business Source License 1.1 (BUSL-1.1)**. It is **not** open source as defined by the OSI, and we don't describe it as such.
-
-### License FAQ
-
-**Why isn't it OSI open source?** BUSL-1.1 places one restriction on production use (next answer), which keeps it outside the Open Source Definition — the BUSL license text itself states it "is not an Open Source license". Rather than blur that line, we say source-available plainly.
-
-**Does it affect personal or team use?** No. The Additional Use Grant in [LICENSE.BSL](LICENSE.BSL) explicitly allows production use; the only carve-out is offering Hive to third parties — hosted or embedded, on a paid basis or under any other revenue-generating arrangement (including paid support) — in a way that competes with Hive's multi-CLI-agent orchestration product. Personal use, internal deployment within your organization, embedding into a non-competitive product, and non-commercial forks are all fine.
-
-**Will it become open source later?** Yes. Each version converts to the **Apache License 2.0** on the Change Date (2030-05-16) or four years after that version's first public release, whichever comes first.
-
-See [LICENSE.BSL](LICENSE.BSL) for the exact terms. Forks and redistributions must preserve [NOTICE](NOTICE), [LICENSE.BSL](LICENSE.BSL), and the applicable license files. The Hive name, logo, and visual identity are not licensed by the source license; see [TRADEMARK.md](TRADEMARK.md) for brand usage boundaries.
+[README.zh.md](./README.zh.md)