ai-agentmanager 1.0.0 → 1.0.2

package/CHANGELOG.md

@@ -0,0 +1,57 @@
+# Changelog
+
+## 1.0.2 (2026-10-28)
+
+- **Resize and expand:** drag the edge of the agent list, or the line between the brief and the terminal; double-click a line to reset it. **Expand** (Ctrl+Shift+E) fills the window with the terminal, shell or browser tab, and **Full screen** fills the screen.
+- **Active agents first:** agents that did real work or got your input in the last day sort to the top, and projects with active agents come before idle ones. Idle agents are dimmed and show how long they've been idle. A restart that resumes an agent doesn't count as activity.
+- **`agentmgr doctor`:** checks Node.js, Claude Code and its sign-in, git, `gh`, the data folder, the daemon's port and Chrome, and says how to fix what's missing.
+- **Clearer first run:** when Claude Code (or another engine) isn't installed or isn't on the daemon's PATH, the agent says so and how to fix it, instead of `spawn claude ENOENT`. Running from a git checkout without `npm install` says to run it, instead of `Cannot find package`.
+- **AI judge:** no longer reads Claude Code's status bar ("accept edits on", "shift+tab to cycle", "update available") as a question, which raised false "waiting on you" items.
+- **Install as an app:** Chrome and Edge can install AI Agent Manager as an app (the install icon in the address bar), so it opens in its own window with a Dock or taskbar icon.
+
+## 1.0.1 (2026-10-26)
+
+- **Name:** the product is now called **AI Agent Manager**, matching the `ai-agentmanager` package. The command is still `agentmgr`.
+- **About:** the version next to the title opens an About box with the release date, author, license, links and this daemon's details; **Check for updates** asks npm for the newest version. `agentmgr about` (`--check`) in a terminal.
+- **Dependencies:** DOMPurify 3.4.17, body-parser 2.4.0, Mermaid 12.
+
+## 1.0.0 (2026-10-25)
+
+- **License:** Apache-2.0 (was MIT).
+- **Remote access is off until you turn it on** (`agentmgr remote on`). Installs that had it on keep it on.
+- **AI judge visibility:** the bottom of the Inbox shows today's calls with **Turn off** / **Turn on**; also `agentmgr judge [on|off]`.
+- **Hub:** `agentmgr hub serve` also listens on this Mac's Tailscale address, and **Add machine** gives a join command other machines can reach (or says why they can't).
+- **Linux:** a clear message when Chrome's sandbox can't start; `browserNoSandbox` to run without it.
+- **Upgrades:** the state file is versioned, backed up at startup, migrated with a backup, and never overwritten by an older version.
+- **Plugins:** policies that can refuse actions, audit listeners, extra API routes and engines on the daemon; sign-in methods, request policies and audit on the hub ([docs/plugins.md](docs/plugins.md)).
+- **Packaging:** `npm i -g ai-agentmanager` (the command is `agentmgr`), `agentmgr --version`.
+- **Installer:** the site's `install.sh` puts the program in `~/.local/share/agentmanager` and never touches `~/.agentmanager`, where your agents and workspaces live. It used to replace that folder.
+- **Start at login:** `agentmgr service install` keeps `AGENTMGR_PLUGINS` and `AGENTMGR_HUB_PLUGINS`.
+- **UI:** long agent names stay on one line, with the buttons below.
+- **Project:** CI on macOS and Linux, SECURITY.md, CONTRIBUTING.md, code of conduct, architecture notes.
+
+## 0.5.0 (2026-10-23)
+
+- **AI judge:** rules decide when to look, a fast model decides what is going on: stuck agents (with a specific nudge), idle screens no rule matched, whether "done" work meets the intent, colliding changes, backlog order and splits, and which alerts interrupt you. Learns from your reactions.
+- **CLI sign-in links:** `railway login`, `gh auth login --web` and similar open where the callback reaches the waiting CLI, from any device.
+- **Live browser tabs:** a real Chrome on the machine, streamed into the tab, with typing, scrolling, popups as tabs, the phone keyboard, sharp frames on retina screens and one-way sound.
+- **Continue terminal sessions:** import Claude Code sessions started with a plain `claude` and continue them as agents.
+
+## 0.4.0 (2026-10-21)
+
+- **Engines:** Codex CLI and Antigravity CLI next to Claude Code, behind one adapter.
+- **Browser tabs:** open any address next to an agent's terminals, relayed over HTTPS to signed-in remote devices.
+- **Human vs AI** review with a second-model critique; optional plan review before an agent implements.
+- **Hub sign-in links:** open a machine's own page signed in, with a one-time ticket.
+
+## 0.3.0 (2026-10-18)
+
+- **Hub:** one place for agents on several machines: fleet view, control, a shared backlog that starts work where there's room, Google sign-in.
+
+## 0.2.0 (2026-10-18)
+
+- **Decision inbox, conflict radar, stuck detection, checkpoints and forks, races.**
+
+## 0.1.x (2026-10-03 to 2026-10-09)
+
+- First release: one background agent per intent, CLI, daemon and web UI, worktrees per agent, briefs, results, phone access, multiple shells and file attachments, swipe to scroll on phones.

package/NOTICE

@@ -1,4 +1,4 @@
-Agent Manager
+AI Agent Manager
 Copyright 2026 Jagadesh Munta
 
 Licensed under the Apache License, Version 2.0 (see LICENSE).

package/README.md

@@ -1,10 +1,10 @@
-# Agent Manager
+# AI Agent Manager
 
 Run one background [Claude Code](https://claude.com/claude-code) agent per intent, and keep track of them from a web UI or the `agentmgr` CLI.
 
 ![Agents grouped by project, with an agent's brief: results, problem, solution, a flow diagram and checks](docs/images/agents.jpg)
 
-![The conflict radar: two agents changed the same lines of README.md, with a suggested order to land them](docs/images/conflict-radar.jpg)
+![The conflict radar: two agents changed the same lines of README.md; the AI judge rates it a collision and suggests which lands first](docs/images/conflict-radar.jpg)
 
 - **Intents in, agents out.** Give one intent or a list (one per line). Each becomes its own `claude` process.
 - **Repo or folder.** Give a git URL (cloned once, then each agent gets its own worktree and branch) or a local folder.
@@ -39,8 +39,11 @@ Run one background [Claude Code](https://claude.com/claude-code) agent per inten
 - **Shells next to each agent.** **Open shell** gives a terminal in the agent's folder for running commands by hand. **+ Shell** opens as many more as you need, each in its own tab.
 - **Browser tabs.** **+ Browser** opens a page as this machine sees it, in a tab next to the agent's terminals. That can be the agent's dev server on `localhost:5173`, a site on its network or VPN, or any address. Local addresses the agent prints are offered as suggestions. It works from your phone or laptop too (see below).
 - **Live browser.** Browser tabs run a real Chrome on this machine and stream it into the tab: you see its screen and your clicks, scrolling, typing and paste go back to it, from the laptop or the phone. Because the page runs here, `localhost` is this machine, sites that refuse to be framed load normally, and popups (a sign-in window) open as tabs of their own and come back when they close. Chrome (or Chromium, Brave, Edge; `browserBin` in config.json picks one) runs headless with its own profile in `~/.agentmanager/browser-profile`, so sign-ins are remembered; it starts on the first view and stops after 15 minutes with nobody watching. Downloads go to `~/Downloads/agentmanager`. A site that still refuses it as a bot may accept `"browserHeadless": false`, which runs Chrome with a real window on this machine's screen. On Linux where Chrome's sandbox can't start (containers, Ubuntu 23.10+ user-namespace restrictions) the tab says so; `"browserNoSandbox": true` runs it without the sandbox, at your own risk. **Lite** on the bar switches a tab to the frame mode (the page loads in your own browser; quicker for a dev server).
-- **CLI sign-in links.** When a terminal prints a sign-in link that returns to a port on this machine (`railway login`, `gh auth login --web`, `gcloud auth login`...), a bar above the terminal offers **Open sign-in**: the link opens in a live browser tab here, so the provider's redirect to `http://127.0.0.1:PORT/callback` reaches the waiting CLI by itself, from any device. It opens on its own if you just typed the command. Without a live browser, it opens a window on your device; from another device you then paste the address you land on (`127.0.0.1:PORT/callback…`) into the bar and Agent Manager delivers it to the CLI, only on the port the link named.
+- **CLI sign-in links.** When a terminal prints a sign-in link that returns to a port on this machine (`railway login`, `gh auth login --web`, `gcloud auth login`...), a bar above the terminal offers **Open sign-in**: the link opens in a live browser tab here, so the provider's redirect to `http://127.0.0.1:PORT/callback` reaches the waiting CLI by itself, from any device. It opens on its own if you just typed the command. Without a live browser, it opens a window on your device; from another device you then paste the address you land on (`127.0.0.1:PORT/callback…`) into the bar and AI Agent Manager delivers it to the CLI, only on the port the link named.
 - **Attach files and screenshots.** Drop files on the terminal, paste a screenshot, or use **📎 Attach**. The file is saved on the daemon's machine and its path is pasted into the terminal, which is how Claude Code picks up images and files.
+- **Your layout.** Drag the edge of the agent list, or the line between the brief and the terminal, to resize them; double-click a line to reset it. **Expand** (Ctrl+Shift+E) fills the window with the terminal, shell or browser tab; **Full screen** fills the screen. Agents active in the last day sort to the top; idle ones are dimmed.
+- **As an app.** In Chrome or Edge, click the install icon in the address bar (or ⋮ → Cast, save and share → Install page as app). AI Agent Manager then opens in its own window with its own Dock or taskbar icon, and the daemon keeps running as before.
+- **About.** The version next to the title opens the About box: release date, author, license, links, and how this daemon runs (data folder, port, Node.js, which `claude`). **Check for updates** asks npm for the newest version. In a terminal: `agentmgr about` (`--check` for updates).
 - **General sessions.** **Ask Claude** starts a session with no repo, folder or intent, for questions. It is tracked and resumable like any other agent.
 
 New in 0.2, for running many agents at once:
@@ -52,6 +55,18 @@ New in 0.2, for running many agents at once:
 - **Checkpoints and forks.** The code (uncommitted work included) and the conversation are saved at the end of every turn. **Fork** starts a new agent from now or from any checkpoint, in its own worktree, to try another direction without losing the first.
 - **Races.** Send one intent to several agents with different models or approaches. Compare their outcome, checks, size of change, cost and a test command run in each worktree, read their diffs side by side, then pick a winner and delete the rest.
 
+## When to use it
+
+Claude Code on its own, including its built-in ways to run work in parallel, is enough for one repo in one sitting. AI Agent Manager is for when that stops being enough:
+
+- **Many sessions across several repos,** running for hours, where you lose track of which one is waiting on you.
+- **Agents that must survive** a closed terminal, a restart or a reboot, and pick up where they left off.
+- **Several agents in one repo,** each on its own worktree and branch, with a warning when two touch the same code.
+- **Keeping up without reading transcripts:** a brief per agent (result, problem, fix, checks) and one inbox for every prompt and question.
+- **From anywhere:** your phone, another computer, or several machines through the hub.
+
+**Trying it costs little.** It runs the same `claude` you already use, with your plan and your repo's `CLAUDE.md` and skills. Sessions you started with `claude` in a terminal can be continued in it (**Import** above the agent list), and you can go back to a plain terminal any time with `claude --resume`.
+
 ## Install
 
 Runs on macOS and Linux; on Windows, use WSL2. Requires Node 20+, `git`, and the `claude` CLI, signed in (run `claude` once). Optional: `gh` (authenticated) for PR discovery by branch and PR state, Chrome (or Chromium, Brave, Edge) for live browser tabs, and Codex (`npm i -g @openai/codex`) as a second engine.
@@ -60,13 +75,13 @@ Runs on macOS and Linux; on Windows, use WSL2. Requires Node 20+, `git`, and the
 
 ```sh
 npm install -g ai-agentmanager          # the latest release
-npm install -g ai-agentmanager@1.0.0    # or a specific one
+npm install -g ai-agentmanager@1.0.2    # or a specific one
 ```
 
 Or from the repository, at a release tag:
 
 ```sh
-git clone --branch v1.0.0 --depth 1 https://github.com/jdmunta/ai-agentmanager-core.git
+git clone --branch v1.0.2 --depth 1 https://github.com/jdmunta/ai-agentmanager-core.git
 cd ai-agentmanager-core
 npm install
 npm link            # optional: puts `agentmgr` on your PATH
@@ -86,9 +101,11 @@ npm link
 | Installed with | Update |
 | --- | --- |
 | npm | `npm install -g ai-agentmanager@latest` |
-| A clone at a release tag | `git fetch --tags && git checkout v1.0.1 && npm install` (the tag you want) |
+| A clone at a release tag | `git fetch --tags && git checkout v1.0.2 && npm install` (the tag you want) |
 | A clone of `main` | `git pull && npm install` |
 
+**Check your setup.** `agentmgr doctor` checks Node.js, Claude Code and its sign-in, git, `gh`, the data folder, the daemon's port and Chrome, and says how to fix anything missing.
+
 ## Quick start on a new computer
 
 **A computer that runs agents.** After installing:
@@ -125,6 +142,7 @@ The hub listens on port 4720, on this Mac and on its Tailscale address (`--host`
 ```sh
 agentmgr ui                                   # start the daemon and open http://127.0.0.1:4717
 agentmgr service install                      # start the daemon at login (launchd / systemd --user)
+agentmgr doctor                               # check Node.js, Claude Code, git, gh, the port; says how to fix
 
 agentmgr add "Fix the flaky login test" -d ~/src/app
 agentmgr add -r https://github.com/org/repo.git \
@@ -207,7 +225,7 @@ Every agent gets **its own worktree and its own branch** (`agent/<name>-<id>`) o
 
 ## Continue sessions started in a terminal
 
-**Import** (next to **Save now** in the agent list) lists the Claude Code sessions you started yourself with `claude` in a terminal on this machine, from the last 7, 30 or 90 days: grouped by folder, with title, first and last ask, branch, size and last activity. Headless runs (`claude -p`, the SDK) and Agent Manager's own agents are left out. Each one you pick becomes an agent in the same folder that continues the same conversation (`--resume`), with the brief, inbox, PRs and usage tracked from then on.
+**Import** (next to **Save now** in the agent list) lists the Claude Code sessions you started yourself with `claude` in a terminal on this machine, from the last 7, 30 or 90 days: grouped by folder, with title, first and last ask, branch, size and last activity. Headless runs (`claude -p`, the SDK) and AI Agent Manager's own agents are left out. Each one you pick becomes an agent in the same folder that continues the same conversation (`--resume`), with the brief, inbox, PRs and usage tracked from then on.
 
 A session still open in a terminal is marked **open in a terminal** (a running `claude` names it) or **maybe open** (a `claude` runs in that folder and the session was active minutes ago). Two places writing one conversation would mix it up, so those continue as a **copy** under a new session ID and the terminal keeps the original. For the same reason, an agent that follows a `/clear` to a new session never picks up a headless run or a session a terminal has open in its folder.
 
@@ -356,7 +374,7 @@ The **Results** card is the first thing in the Brief panel, and `agentmgr show`
 - **Blockers first, in red.**
 - **What was delivered.**
 
-It combines what the agent wrote under `## Results` with what Agent Manager tracks itself:
+It combines what the agent wrote under `## Results` with what AI Agent Manager tracks itself:
 
 - PRs (with their state).
 - Failing checks.
@@ -463,7 +481,7 @@ The data set is small.
 
 ## Conflict radar
 
-For each agent with its own branch, Agent Manager works out which files and line ranges its branch changed since it branched, including uncommitted and new files. Agents working in the same repository (the same shared clone or source folder) that touch the same file are flagged:
+For each agent with its own branch, AI Agent Manager works out which files and line ranges its branch changed since it branched, including uncommitted and new files. Agents working in the same repository (the same shared clone or source folder) that touch the same file are flagged:
 
 - **same lines**: both edit the same region, within a few lines (likely a merge conflict). Only judged when both branched from the same commit.
 - **same file**: both edit the file, in different places.
@@ -509,7 +527,7 @@ Fixed rules are cheap but miss context: three identical failures can be a conver
 
 ## Checkpoints and forks
 
-At the end of each turn, Agent Manager snapshots the agent's working tree as a commit under `refs/agentmgr/<agent>/<n>`. This doesn't touch the agent's branch, index or files. It records how far the conversation had got alongside. The last 40 are kept (`maxCheckpoints`); deleting the agent removes them.
+At the end of each turn, AI Agent Manager snapshots the agent's working tree as a commit under `refs/agentmgr/<agent>/<n>`. This doesn't touch the agent's branch, index or files. It records how far the conversation had got alongside. The last 40 are kept (`maxCheckpoints`); deleting the agent removes them.
 
 **Fork** (or `agentmgr fork <agent> [-c n]`) creates a new agent:
 
@@ -608,7 +626,7 @@ Or use **Remote access** in the header of the UI on this computer.
 
 Agents run Claude Code by default. With OpenAI's Codex CLI installed (`npm i -g @openai/codex`, signed in), an agent can run Codex instead: `agentmgr add --engine codex …`, or the **Engine** picker in New agent (shown once a second engine is installed). Everything else works the same way: worktrees, the brief and questions, the inbox (Codex's approval menus included), token usage, stuck detection, PR tracking, Explain, the backlog and the hub. Codex records no cost, and planning while a repo clones and forks are Claude-only for now. Set `"engine": "codex"` in config.json to make it the default; `engines.codex.bin` points at another binary. On the hub, each machine reports the engines it has (`engine:codex`), so shared backlog work can ask for one. See [docs/engines.md](docs/engines.md).
 
-Google's **Antigravity CLI** (`agy`, signed in with your Google account) works the same way: `--engine antigravity`. It replaced Gemini CLI for personal Google accounts in June 2026. Agent Manager adopts the conversation agy starts, resumes it with `--conversation`, reads token usage, commands and file writes from its transcript, shows its permission menus (commands, file changes, access outside the folder) in the inbox, pre-trusts agent folders in agy's settings, and runs Explain in agy's print mode. agy asks before writing the brief too, unless the agent runs in `acceptEdits` mode. `engines.antigravity.bin` points at another binary.
+Google's **Antigravity CLI** (`agy`, signed in with your Google account) works the same way: `--engine antigravity`. It replaced Gemini CLI for personal Google accounts in June 2026. AI Agent Manager adopts the conversation agy starts, resumes it with `--conversation`, reads token usage, commands and file writes from its transcript, shows its permission menus (commands, file changes, access outside the folder) in the inbox, pre-trusts agent folders in agy's settings, and runs Explain in agy's print mode. agy asks before writing the brief too, unless the agent runs in `acceptEdits` mode. `engines.antigravity.bin` points at another binary.
 
 ## Several machines: the hub
 
@@ -697,8 +715,8 @@ Usage comes from the session transcripts and is refreshed every few seconds whil
 - **Open shell** (or `agentmgr shell <agent>`) starts `$SHELL -l` in the agent's working folder. It shows as a **Shell 1** tab next to the **Claude** tab in the terminal pane; **+ Shell** (or `agentmgr shell <agent> -n 2`) opens more, and **×** on a tab closes that shell. Shells live as long as the daemon and don't start Claude.
 - **+ Browser** opens a tab on an address: a port (`5173`), a local address (`localhost:3000/app`), something on the machine's network (`10.0.0.7:8080`, `staging.internal`) or any site (`example.com`, which defaults to https). Tabs are kept with the agent, so every device sees them, and **×** closes one.
   - **On this computer** the tab loads the address directly. Many public sites refuse to appear inside another page, so use **↗** for those.
-  - **From another device** (remote access), Agent Manager gives each site its own HTTPS port. That port relays to the site as the machine sees it, so you can check from your phone what the agent built or what the machine can reach. Absolute links, redirects and hot-reload WebSockets on the same site keep working, and the site's "don't show me in a frame" headers are dropped. A link or redirect to a different site leaves the relay.
-  - **Safety:** the relay serves only signed-in devices. It never relays to Agent Manager's own ports on any of the machine's addresses, and it removes Agent Manager's sign-in cookie before forwarding. Sites other than localhost must present a valid certificate. The relays close when remote access is turned off.
+  - **From another device** (remote access), AI Agent Manager gives each site its own HTTPS port. That port relays to the site as the machine sees it, so you can check from your phone what the agent built or what the machine can reach. Absolute links, redirects and hot-reload WebSockets on the same site keep working, and the site's "don't show me in a frame" headers are dropped. A link or redirect to a different site leaves the relay.
+  - **Safety:** the relay serves only signed-in devices. It never relays to AI Agent Manager's own ports on any of the machine's addresses, and it removes AI Agent Manager's sign-in cookie before forwarding. Sites other than localhost must present a valid certificate. The relays close when remote access is turned off.
   - If a tab stays blank on a device, open it once with **↗** and accept the certificate there.
 - **Ask Claude** (or `agentmgr ask`) creates a `general` agent. All general sessions share `~/.agentmanager/general`, so Claude's folder-trust prompt only appears the first time.
 
@@ -762,7 +780,7 @@ npm test    # unit tests + end-to-end daemon tests against a stub claude (test/f
 
 - How the code fits together: [docs/architecture.md](docs/architecture.md). Extending it from a separate package (policies, audit, routes, engines, hub sign-in): [docs/plugins.md](docs/plugins.md). How to contribute: [CONTRIBUTING.md](CONTRIBUTING.md). Changes per release: [CHANGELOG.md](CHANGELOG.md).
 - Security model and how to report a problem privately: [SECURITY.md](SECURITY.md).
-- Agent Manager sends no telemetry.
-- Agent Manager runs the agent CLIs you install and sign in to (Claude Code, Codex, Antigravity) with your own accounts. Use them within your provider's terms.
+- AI Agent Manager sends no telemetry. The only request it makes on its own behalf is **Check for updates**, when you click it.
+- AI Agent Manager runs the agent CLIs you install and sign in to (Claude Code, Codex, Antigravity) with your own accounts. Use them within your provider's terms.
 - Maintained in spare time. Issues and pull requests are welcome; replies may take a few days.
 - Licensed under the [Apache License 2.0](LICENSE).

package/SECURITY.md

@@ -4,9 +4,9 @@
 
 Please report security issues privately through GitHub: **Security → Report a vulnerability** on this repository. Don't open a public issue. You'll get a reply within a few days, and a fix or a plan before anything is disclosed.
 
-## What Agent Manager is, from a security point of view
+## What AI Agent Manager is, from a security point of view
 
-Agent Manager runs coding agents (Claude Code, Codex, Antigravity) **as your user, on your machine**, in real terminals. Anyone who can drive Agent Manager can run commands as you. The design goal is that only you can drive it, from this machine, unless you deliberately open it up.
+AI Agent Manager runs coding agents (Claude Code, Codex, Antigravity) **as your user, on your machine**, in real terminals. Anyone who can drive AI Agent Manager can run commands as you. The design goal is that only you can drive it, from this machine, unless you deliberately open it up.
 
 ### Trust boundaries
 
@@ -16,7 +16,7 @@ Agent Manager runs coding agents (Claude Code, Codex, Antigravity) **as your use
 | Remote access (`https://<ip>:4718`) | Nobody: **off until you run `agentmgr remote on`** | HTTPS with a certificate made on this machine. Every API call needs a signed-in device session (sign-in with the access token or its QR code; sessions last 30 days, can be revoked one by one, and rotating the token signs everyone out). Only this machine's own addresses are accepted as `Host`. Turning remote access on or off, the token, devices and shutdown are local-only. |
 | Hub (`agentmgr hub serve`, port 4720) | This machine and its Tailscale address | One admin token (or Google sign-in limited to listed emails); browsers get a 30-day session cookie. Plain `http://` is accepted only on loopback or Tailscale, which encrypts traffic; anything else must be `https://`. |
 | A machine joined to a hub | The hub, over a connection the machine opens | Ed25519 key per machine (private key in `~/.agentmanager/hub-link.json`, mode 600); each connection signs a fresh challenge. The machine decides what the hub may do (`hub.allow`, default `view` only), checks every request itself, matches agents by exact ID, runs only a fixed list of actions (never deletes) and logs each request and refusal to `~/.agentmanager/hub-audit.log`. |
-| Site relays (browser tabs from another device) | Signed-in remote devices | Never relay to Agent Manager's own ports; its sign-in cookie is stripped before forwarding; sites other than localhost must present a valid certificate; relays close when remote access is turned off. |
+| Site relays (browser tabs from another device) | Signed-in remote devices | Never relay to AI Agent Manager's own ports; its sign-in cookie is stripped before forwarding; sites other than localhost must present a valid certificate; relays close when remote access is turned off. |
 | CLI sign-in callbacks | The UI | Delivered only to the loopback port the sign-in link itself named. |
 
 ### What is stored, and where
@@ -30,12 +30,12 @@ Everything lives in `~/.agentmanager/` (or `$AGENTMGR_HOME`):
 - `browser-profile/`: the live browser's Chrome profile. Sites you sign in to there stay signed in, as in any browser.
 - `scrollback/`, `briefs/`, `state.json`: terminal output and agent state. These can contain anything an agent printed, including secrets it read.
 
-Agent Manager sends **no telemetry**. It talks to the network only for what you set up: git remotes, GitHub (`gh`), Slack, a hub you joined, and the agents' own model providers.
+AI Agent Manager sends **no telemetry**. It talks to the network only for what you set up: git remotes, GitHub (`gh`), Slack, a hub you joined, and the agents' own model providers. **Check for updates** in the About box (or `agentmgr about --check`) asks the npm registry for the newest version, only when you click it.
 
 ### Things to be aware of
 
-- **Agents act as you.** Each agent's permission mode (for Claude: `default`, `acceptEdits`, `plan`, `auto`, `bypassPermissions`) is passed to the engine; Agent Manager doesn't sandbox agents beyond that. Run agents in folders and with modes you'd be comfortable running the engine in by hand.
-- **Other processes running as your user** can call the local API, just as they could run `claude` themselves. Agent Manager doesn't defend against malware already running as you.
+- **Agents act as you.** Each agent's permission mode (for Claude: `default`, `acceptEdits`, `plan`, `auto`, `bypassPermissions`) is passed to the engine; AI Agent Manager doesn't sandbox agents beyond that. Run agents in folders and with modes you'd be comfortable running the engine in by hand.
+- **Other processes running as your user** can call the local API, just as they could run `claude` themselves. AI Agent Manager doesn't defend against malware already running as you.
 - **The AI judge** sends short summaries of an agent's screen, activity and brief to the same engine the agents use (by default Claude `haiku`), as separate calls. Turn it off with `agentmgr judge off`.
 - **Remote access on an untrusted network** (café Wi-Fi) exposes the sign-in page on your local network. Leave it off there, or use Tailscale and the hub instead.
 

package/bin/agentmgr-hub.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// The hub on its own, for hosts without the rest of Agent Manager (Railway, a container).
+// The hub on its own, for hosts without the rest of AI Agent Manager (Railway, a container).
 // Locally, "agentmgr hub serve" does the same.
 import { startHub } from '../src/hub.js';
 

package/bin/agentmgr.js

@@ -1,4 +1,11 @@
 #!/usr/bin/env node
-import { main } from '../src/cli.js';
-
-main(process.argv);
+// Dependencies are loaded behind a check, so a git checkout without `npm install` says so.
+try {
+  const { main } = await import('../src/cli.js');
+  await main(process.argv);
+} catch (err) {
+  if (err?.code !== 'ERR_MODULE_NOT_FOUND' || !/Cannot find package/.test(err.message)) throw err;
+  const dir = new URL('..', import.meta.url).pathname;
+  console.error(`agentmgr: dependencies are missing (${err.message.match(/'([^']+)'/)?.[1] ?? 'a package'}).\nRun \`npm install\` in ${dir} and try again.`);
+  process.exit(1);
+}

package/docs/architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-Agent Manager is one long-running **daemon** per machine. It owns every agent's terminal and state. The **web UI** and the **CLI** are clients of its HTTP and WebSocket API. Optionally, daemons on several machines connect out to a **hub**.
+AI Agent Manager is one long-running **daemon** per machine. It owns every agent's terminal and state. The **web UI** and the **CLI** are clients of its HTTP and WebSocket API. Optionally, daemons on several machines connect out to a **hub**.
 
 ```
  browser (UI) ──┐                       ┌── claude / codex / agy in PTYs (one per agent, plus shells)

package/docs/distributed.md

@@ -4,7 +4,7 @@ Status: phases 1–3 built (0.3, branch `v0.3-fleet`) · Phases 4–5: planned
 
 ## Problem
 
-Agent Manager runs every agent on the machine its daemon runs on. Once you have agents on more than one machine (a Mac mini that is always on, a laptop, a cloud VM with more cores, a teammate's box), you get one UI per machine, one inbox per machine, and a backlog that can't use spare capacity elsewhere. Overlaps between agents on different machines go unnoticed until merge time.
+AI Agent Manager runs every agent on the machine its daemon runs on. Once you have agents on more than one machine (a Mac mini that is always on, a laptop, a cloud VM with more cores, a teammate's box), you get one UI per machine, one inbox per machine, and a backlog that can't use spare capacity elsewhere. Overlaps between agents on different machines go unnoticed until merge time.
 
 ## Goals
 

package/docs/engines.md

@@ -2,7 +2,7 @@
 
 Status: phase 1, Codex and Antigravity built. Gemini CLI dropped: since June 18, 2026 it no longer serves personal Google accounts, and Antigravity CLI (`agy`, `src/engines/antigravity.js`, checked against 1.4.3, fixtures in `test/fixtures/antigravity/`) replaced it. 0.4 (branch `v0.4-engines`) · 2026-10-18. Targets the current releases of each CLI, checked in phase 1.
 
-Agent Manager runs every agent with Claude Code. If Anthropic has an outage, a rate limit hits, or prices change, every agent stops at once. Running agents on other engines as well makes the fleet resilient across providers, and lets each task use the engine that suits it.
+AI Agent Manager runs every agent with Claude Code. If Anthropic has an outage, a rate limit hits, or prices change, every agent stops at once. Running agents on other engines as well makes the fleet resilient across providers, and lets each task use the engine that suits it.
 
 ## Goals
 
@@ -14,7 +14,7 @@ Agent Manager runs every agent with Claude Code. If Anthropic has an outage, a r
 ## Non-goals
 
 - **Moving a live conversation between engines.** Conversations stay with their engine. A task can continue on another engine through a handoff (below), which carries the work but not the chat history.
-- **Editor-based agents** (Antigravity, Cursor, and so on). Agent Manager drives command-line agents in a terminal.
+- **Editor-based agents** (Antigravity, Cursor, and so on). AI Agent Manager drives command-line agents in a terminal.
 - **Running models directly through APIs.** Each engine keeps its own CLI, sign-in, tools and safety settings.
 
 ## What is Claude-specific today
@@ -91,9 +91,9 @@ Gemini CLI flags are checked against 0.64.0 (`test/fixtures/gemini/help-0.64.0.t
 
 ### Permission modes
 
-Agent Manager's three modes map to each engine's own approval settings. The hub's rule stays: no mode that skips all prompts can be started from the hub.
+AI Agent Manager's three modes map to each engine's own approval settings. The hub's rule stays: no mode that skips all prompts can be started from the hub.
 
-| Agent Manager | Claude Code | Codex CLI | Gemini CLI |
+| AI Agent Manager | Claude Code | Codex CLI | Gemini CLI |
 | --- | --- | --- | --- |
 | `default` (ask) | `default` | `--sandbox workspace-write --ask-for-approval on-request` (0.163 only has `on-request` and `never`) | `--approval-mode default` |
 | `acceptEdits` | `acceptEdits` | the same: edits inside the workspace never ask | `--approval-mode auto_edit` |
@@ -107,7 +107,7 @@ The brief and questions files are what make an agent reviewable from the inbox,
 - **Instructions:** today they go in `--append-system-prompt`. Codex and Gemini have no per-launch system prompt flag, so the instructions go in the first message of a new session, and are repeated briefly on resume (in the resume message where the engine accepts one). Writing them into the repo's `AGENTS.md`/`GEMINI.md` is rejected: that would change the user's repo.
 - **Writing outside the repo:** Codex's sandbox only writes inside the workspace by default. Options, in order of preference:
   1. Allow the brief folder as an extra writable root (`--add-dir` or `writable_roots`).
-  2. Have the agent write `.agentmgr/BRIEF.md` inside its worktree, add `.agentmgr/` to the worktree's local git excludes (`.git/info/exclude` of the worktree, never the repo's `.gitignore`), and have Agent Manager read it from there.
+  2. Have the agent write `.agentmgr/BRIEF.md` inside its worktree, add `.agentmgr/` to the worktree's local git excludes (`.git/info/exclude` of the worktree, never the repo's `.gitignore`), and have AI Agent Manager read it from there.
 - **Parsing** (`parseBrief`, `parseQuestions`) is already engine-neutral.
 
 ### Usage, activity and stuck detection

package/docs/plugins.md

@@ -1,6 +1,6 @@
 # Plugins
 
-A plugin extends Agent Manager from a separate package, without changing its code: add policies that can refuse actions, listen to what happens (for an audit trail), serve extra API routes, add an agent engine, or (on the hub) add a sign-in method.
+A plugin extends AI Agent Manager from a separate package, without changing its code: add policies that can refuse actions, listen to what happens (for an audit trail), serve extra API routes, add an agent engine, or (on the hub) add a sign-in method.
 
 ## Loading
 
@@ -10,7 +10,7 @@ A plugin extends Agent Manager from a separate package, without changing its cod
 { "plugins": ["@acme/agentmanager-policy", "./plugins/audit.js"] }
 ```
 
-Package names are resolved from Agent Manager's install; paths are relative to `~/.agentmanager` (`~` works too).
+Package names are resolved from AI Agent Manager's install; paths are relative to `~/.agentmanager` (`~` works too).
 
 **Hub:** `AGENTMGR_HUB_PLUGINS=@acme/agentmanager-sso,./plugins/hub-audit.js` (paths relative to the hub's state folder).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-agentmanager",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Run background coding agents (Claude Code, Codex) per intent, and keep track of them from a web UI, your phone or the CLI",
   "keywords": [
     "claude",
@@ -19,6 +19,7 @@
   "bugs": {
     "url": "https://github.com/jdmunta/ai-agentmanager-core/issues"
   },
+  "author": "Jagadesh Munta (https://github.com/jdmunta)",
   "license": "Apache-2.0",
   "type": "module",
   "bin": {
@@ -33,7 +34,8 @@
     "README.md",
     "LICENSE",
     "NOTICE",
-    "SECURITY.md"
+    "SECURITY.md",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "start": "node bin/agentmgr.js serve",
@@ -47,10 +49,10 @@
     "@xterm/addon-fit": "^0.11.0",
     "@xterm/xterm": "^6.0.0",
     "commander": "^15.0.0",
-    "dompurify": "^3.4.16",
+    "dompurify": "^3.4.17",
     "express": "^5.2.1",
     "marked": "^18.0.14",
-    "mermaid": "^11.17.2",
+    "mermaid": "^12.2.0",
     "node-pty": "^1.1.0",
     "qrcode": "^1.5.4",
     "ws": "^8.22.0"