@xingjisoft/neutrino 0.3.0 → 0.4.1

package/web/README.md

@@ -15,14 +15,17 @@ A small, dependency-free single page app that is served by the Neutrino CLI at
 - switch the workspace between every known folder and **All directories**;
 - switch the provider, model and intensity for the next turn;
 - edit every terminal setting — defaults, interface language, plan-first turns,
-  default approval mode, context compression, reviewer and Web password;
+  default approval mode, context compression, reviewer, Web password, and LAN
+  access;
 - switch the interface between English and 简体中文, instantly and persistently;
 - open the same plan / token card as the terminal's `ⓘ`, clear a conversation,
-  delete a saved transcript, and review other agents' read-only history;
+  delete a saved transcript, and review or migrate other agents' history;
 - drive the running conversation: pause / resume the current turn and send new
   messages (they queue while the agent is busy);
 - pick up a saved conversation in the browser and keep chatting, even when no
-  terminal is running.
+  terminal is running;
+- run the console as a detached background service, so conversations started in
+  the browser survive closing the terminal and the CLI process.
 
 Nothing needs to be built — these are plain `.html`, `.css` and `.js` files.
 
@@ -35,7 +38,13 @@ neutrino
 ```
 
 Use `--port` to move it, `--no-web` to skip it for that run, or turn it off
-permanently in the terminal's **Settings → Web console**.
+permanently in the terminal's **Settings → Web console**. LAN access can be
+switched on and off at any time in the browser's **Settings → Web access**
+without restarting anything.
+
+To keep the console alive after the terminal exits, turn on **Settings →
+Background residency** in either workspace, or use `neutrino background` — see
+[Background residency](#background-residency).
 
 Or serve only the saved history, without a terminal:
 
@@ -47,6 +56,44 @@ npm run web
 
 Then open <http://127.0.0.1:8765>.
 
+## Background residency
+
+Background residency is off by default. It is a property of the process, so the
+regular and Pro workspaces share it; changing it in either page (or in the
+terminal's **Settings → Background residency**) applies immediately, including
+to browser tasks already in progress.
+
+With it on, closing the terminal or exiting the CLI does not interrupt browser
+conversations. With it off, the console follows its attached terminals and lets
+current browser tasks finish before it shuts down. The terminal's own
+conversations remain local to the terminal. Terminal and standalone launches
+share one Web console; a standalone launch reports a conflict if its requested
+port, interface or password setting differs from the running console. A ready
+service can be managed without a terminal:
+
+```sh
+neutrino background start     # detach the web console
+neutrino background status    # show its pid and address
+neutrino background open      # open it in the default browser
+neutrino background stop      # stop it
+```
+
+On Windows the service adds a notification-area icon using the same orbit badge
+as the regular console's top-left logo. Click it to open the console; its menu
+opens or stops the service. `--no-tray` suppresses it, and `NEUTRINO_NO_TRAY=1`
+does the same for automation. The service records its pid, address and a random
+management token in `~/.neutrino/background.json` (mode `0600`) and appends
+startup/stop diagnostics to `~/.neutrino/background.log`. The token protects
+`/api/background/ping` and `/api/background/stop`; it is never sent to a
+browser.
+
+When a console is mounted by the terminal and the setting is off, the first
+browser to open it is offered **建议开启后台常驻，避免误触中断任务** with a
+highlighted **开启** and **取消**. Either answer consumes the invitation for
+that CLI run — a reload does not ask again. **开启** applies immediately to the
+current browser tasks. The invitation is never shown when residency is already
+on or by a bare `neutrino web` server.
+
 ## Using it from another device
 
 The server binds to loopback by default. To open it from your phone or another
@@ -58,6 +105,17 @@ neutrino --host 100.64.0.7                   # TUI + web UI, one specific addres
 neutrino web --port 8765 --lan               # headless web UI, every interface
 ```
 
+You can also switch this at runtime from the browser: **Settings → Web access →
+Allow access from other devices (LAN, 0.0.0.0)**. The server re-binds the same
+port to `0.0.0.0` immediately — no restart, and the tab you are using keeps its
+open connections — and saves the choice in `config.json`, so the next launch
+starts on the LAN too. Turning the switch off returns the console to
+`127.0.0.1`. An explicit `--host`/`--lan` decides the interface at startup; the
+in-page switch takes over from there for the running process.
+
+The console can read every transcript and drive an agent with shell access, so
+keep the Web password on: anyone who can reach the port can use it.
+
 Startup prints the addresses to open:
 
 ```
@@ -108,6 +166,61 @@ headers, token URLs, `--token` and `NEUTRINO_WEB_TOKEN` are no longer used.
 Static files and the login/logout routes stay public. `--no-auth` explicitly
 disables password login.
 
+## Pro workspace
+
+The composer has a preset card at its bottom-right. Open it and drag the slider
+to select a team. There are eight roles: main, reasoning, frontend, backend,
+approval, planning, modeling and reserved image generation. Presets are copied
+unchanged from the supplied example into `~/.neutrino/pro/model.json` on first
+use. Edit role assignments there; **Settings** controls the default preset and
+maximum delegation depth (10 by default).
+
+Every task checks all active models with a small completion request. Unavailable
+roles recurse down to lower presets independently, and a popup shows the
+replacements. These changes are task-local. The planner then writes the plan
+before main execution; nested specialist calls and commands use the same
+approval gate, with the approval role providing automated reviews.
+
+Pro API additions: settings return `pro.presets`, `pro.preset` and
+`pro.max_recursion_depth`; settings patches accept `pro_preset` and
+`pro_max_recursion_depth`. New and resumed conversations accept `pro_preset`.
+`POST /pro/api/live/:key/pro-preset` with `{"preset":"medium"}` changes an idle
+or paused conversation. Snapshots include `pro.checking`, effective `pro.models`,
+`pro.fallbacks`, `pro.checkId` and any `pro.error`.
+
+The console has two workspaces. The regular one lives at `/`; the isolated **Pro** workspace lives at `/pro`. Both use the same page, the
+same login cookie and the same model catalog, but nothing else is shared:
+
+- **Conversations** — Pro transcripts are saved under
+  `~/.neutrino/pro/session/`, so neither sidebar ever lists the other
+  workspace's history. Live sessions are separated too: a Pro tab cannot read,
+  stream, drive or close a regular session, and vice versa.
+- **Settings** — Pro has its own `~/.neutrino/pro/config.json` with its own
+  language, sound alerts, default preset, delegation depth and recent folders.
+  `~/.neutrino/pro/model.json` records role models, effort and context capacities;
+  provider credentials stay in the shared ordinary model catalog.
+- **Shared on purpose** — the Web password, the approval policy (default
+  approval mode, extreme-risk auto-approval) and the console's LAN access. They
+  protect or configure the whole machine, so both workspaces, the terminal and
+  every browser read and write the same values.
+
+In the regular console, click the orbit badge to the left of the **Neutrino**
+title (or the blue hint pointing at it). A `#151515` curtain fades in and plays
+the `neutrino-pro.gif` wordmark in the centre; after three seconds it fades out
+onto `/pro`. The X on the blue hint dismisses it permanently for this browser.
+In the terminal, the **启用Pro模式** box below the status bar starts the Web
+console if necessary and opens `/pro` in the default browser. Pro mode uses the
+static `web/neutrino.png` wordmark as its top-left logo, renames the sidebar
+brand to **Neutrino Pro**, and puts an **Exit Pro mode / 返回普通模式** button
+at the top-right of the workspace, which returns to the regular console at
+`/`. The rest of the workspace is identical to the regular one. The interface
+is available in English and 简体中文 in both workspaces (each remembers its own
+choice).
+
+Every API route below has an isolated twin under `/pro/api/` — for example,
+`/pro/api/overview`, `/pro/api/settings` and `/pro/api/live/:key/stream`. The
+login/logout routes are shared and stay unprefixed.
+
 ## Models and settings
 
 Open a conversation to see the **Provider**, **Model** and **Thinking**
@@ -124,12 +237,16 @@ removed can still be continued.
 The **Settings** (gear) button in the sidebar opens the interface language,
 plan-first turns, the default approval mode, defaults for new conversations, the
 context compression threshold, the approval reviewer model, sound alerts, the
-extreme-risk automatic approval option, and the Web password. Save settings
-explicitly; cancelling leaves the saved values intact. Conversation model changes
-are separate from these defaults. Models come from the same catalog as the
-terminal, and API keys stay on the server. Configure missing keys in the terminal
-model screen first. Intensity uses the same Low–Ultra sampling settings as the
-terminal.
+extreme-risk automatic approval option, background residency, LAN access, and
+the Web password. Save settings explicitly; cancelling leaves the saved values
+intact. Conversation model changes are separate from these defaults. Models come
+from the same catalog as the terminal, and API keys stay on the server. Configure
+missing keys in the terminal model screen first. Intensity uses the same
+Low–Ultra sampling settings as the terminal, and both only offer the levels the
+selected model declares in `model.json`. The regular and [Pro](#pro-workspace)
+workspaces keep their own copy of every setting here except the approval policy,
+the Web password, LAN access and background residency, which belong to the whole
+process.
 
 ## New conversations and working directories
 
@@ -154,9 +271,11 @@ that has no conversations yet is still listed after a restart.
 
 The sidebar footer and **Settings → Interface** both offer English and 简体中文.
 The change is applied to the already-open page (labels, messages, status line,
-plan card and dialogs) without a reload, is stored in `config.json`, and is
-shared by every browser. The terminal UI stays in English. New conversation
-content, of course, remains in the language the model writes.
+plan card and dialogs) without a reload, is stored in the workspace's
+`config.json`, and is shared by every browser showing that workspace. The
+regular and Pro workspaces remember their own choice. The terminal UI stays in
+English. New conversation content, of course, remains in the language the model
+writes.
 
 ## History vs. live sessions
 
@@ -198,6 +317,14 @@ the complete transcript in the conversation pane with a `read-only` badge. The
 sources are the same as the terminal's history browser; OpenCode requires Node.js
 22.13+ because it reads its SQLite database through `node:sqlite`.
 
+Click **Migrate session** at the bottom right of an opened transcript to convert
+its readable user/assistant text into a new, saved Neutrino conversation. The
+copy opens immediately in the same working directory, using the current
+Neutrino model (or the current Pro preset on `/pro`). The source is unchanged.
+Foreign system prompts, tool records and non-text attachments are not imported.
+The button is disabled while copying; a failed migration leaves the source open
+with an error so you can retry.
+
 ## Plan-first turns
 
 A browser-owned turn is planned before it runs, exactly like a turn in the
@@ -254,13 +381,17 @@ to know whether a conversation is driven by the terminal or by the server.
 | GET | `/api/fs?path=…` | Folder listing for the picker (folders only, roots, parent) |
 | POST | `/api/fs/mkdir` | Create `{ "path": "…" }` and return the new path |
 | POST | `/api/conversations` | Start `{ cwd, selection?, approval_mode? }`, returns `{ key, snapshot }` |
-| GET | `/api/settings` | Model catalog, languages and public settings; no credentials |
-| POST | `/api/settings` | Save validated `{ selection?, settings? }`, including `language`, `plan_first`, `approval_mode` and `web_password` |
+| GET | `/api/settings` | Model catalog (each model lists its supported intensities), languages, public settings, the live bind address (`web_host`, `web_urls`) and the background state (`background`, `background_running`, `background_url`, one-time `background_prompt`); no credentials |
+| POST | `/api/settings` | Save validated `{ selection?, settings? }`, including `language`, `plan_first`, `approval_mode`, `web_lan`, `background` and `web_password` |
+| POST | `/api/background/dismiss` | Consume the one-time background-residency invitation for this console run |
+| GET | `/api/background/ping` | Management probe of a detached service; requires `Authorization: Bearer <background.json token>` |
+| POST | `/api/background/stop` | Ask a detached service to shut down; same bearer token |
 | GET | `/api/session/:id` | One saved transcript |
 | POST | `/api/session/:id/continue` | Resume a transcript with optional `{ selection }`, returns `{ key }` |
 | POST | `/api/session/:id/delete` | Delete a saved, non-running transcript |
 | GET | `/api/agents/:agent/sessions?cwd=…` | Read-only sessions from Claude Code / Codex / OpenCode |
 | GET | `/api/agents/:agent/sessions/:id` | Read-only messages of one other-agent session |
+| POST | `/api/agents/:agent/sessions/:id/migrate` | Copy a source in `cwd` into a saved native conversation and return its live key; accepts optional `selection` or Pro `pro_preset` |
 | GET | `/api/live/:key` | Snapshot of a live session |
 | GET | `/api/live/:key/stream` | SSE stream of a live session |
 | POST | `/api/live/:key/pause` | Pause the running turn |
@@ -277,7 +408,10 @@ to know whether a conversation is driven by the terminal or by the server.
 
 Conversation and settings routes require the login cookie; see
 [Authentication](#authentication). `OPTIONS` is answered unauthenticated so
-preflights are not blocked, and it returns no data.
+preflights are not blocked, and it returns no data. The `/api/background/*`
+management routes are the exception: they exist only in a detached service and
+authenticate with the bearer token from `background.json`, because the CLI and
+the tray icon have no browser cookie.
 
 ### Approval requests