@mmmbuto/nexuscrew 0.8.2 → 0.8.4

package/README.md

@@ -16,7 +16,7 @@ panes, windows. tmux does the work; the browser is just a faithful client.
 
 ---
 
-## What it is (v0.8.2 "Simple Federated Hydra")
+## What it is (v0.8.4 "Simple and Clean")
 
 - Runs a small server on the host where your tmux sessions live.
 - Each attach spawns a real PTY running `tmux attach` and bridges its bytes over a WebSocket
@@ -27,9 +27,10 @@ panes, windows. tmux does the work; the browser is just a faithful client.
 - **Multi-window decks**: named workspaces at `/deck/<name>` — one browser window per
   monitor, each with its own remembered tile layout. The focused tile is the size owner;
   everything else attaches with `ignore-size`.
-- **Multi-node**: register other hosts as nodes over dedicated restricted SSH tunnels and
-  see their tmux fleets in the same UI. Per-node groups, remote attach, and file exchange
-  all travel through a single-origin `/node/<name>` proxy using one local token.
+- **Federated Hydra inventory**: connect existing NexusCrew installations through the SSH
+  configuration you already control and see local, direct, and relayed tmux fleets in one UI.
+  Route labels show where every session lives; creation, attach, files, lifecycle and Fleet
+  management use the selected location through a scoped single-origin route.
 - **Settings and wizard**: manage roles, nodes, token rotation, and service regeneration
   from the UI; a skippable first-run wizard guides initial setup.
 - **Session lifecycle from the UI**: create sessions (name + cwd + an allowlisted preset)
@@ -41,6 +42,8 @@ panes, windows. tmux does the work; the browser is just a faithful client.
 - **i18n**: English, Italian, Spanish — follows your browser language, switchable in the UI.
 - **localhost-only**: the server binds `127.0.0.1` and refuses any non-loopback bind.
 - **Stateless**: tmux *is* the persistence. No database, no accounts.
+- **Mobile terminal controls**: long-press begins local text selection, drag extends it, and
+  the composer send button keeps the software keyboard open for the next message.
 - **Universal**: a PTY is a PTY — a coding agent, a REPL, a plain shell, anything tmux holds.
 
 ## Screenshots
@@ -70,6 +73,12 @@ Responses-only. New custom credentials are read only from the environment variab
 the PWA; NexusCrew never stores the secret value. Existing Z.AI A/P and Ollama Cloud profiles
 retain their backwards-compatible credential loading.
 
+Managed engines expose a permission selector. New Claude engines (native, Z.AI, Ollama, or
+custom) default to **Bypass permissions** and launch with
+`--dangerously-skip-permissions`; choose **Standard permissions** to disable it. New Codex and
+Codex-VL engines default to Standard and offer an explicit opt-in for
+`--dangerously-bypass-approvals-and-sandbox`. Pi keeps its native permission behavior.
+
 Custom argv-based engines remain supported. Their command, environment, cwd, and prompt are
 validated against a strict trust boundary and launched without a shell.
 
@@ -101,8 +110,7 @@ off. Set `NEXUSCREW_FLEET=0` to disable it entirely.
 - **tmux** on the host (3.4+; the non-destructive `ignore-size` attach is honored on 3.4 and
   later)
 - A PTY backend is resolved automatically per platform: Darwin ARM64/x64 and Linux ARM64/x64
-  prebuilds, the native Android ARM64 provider on Termux, and `node-pty` as the
-  build-from-source fallback.
+  scriptless prebuilds, including the native Android ARM64 provider on Termux.
 
 ## Access model — read this
 
@@ -139,7 +147,8 @@ PWA token never crosses a peer link.
 A relay controls what its peers can see. The default is the whole network; a peer can be reduced
 to relay-only or a selected set. HTTP and WebSocket routing enforce that policy at every hop,
 with stable instance IDs, cycle rejection and a four-hop ceiling. Session creation, terminal,
-files and termination work on Local or any reachable route; Fleet remains local to each node.
+files, termination, and Fleet editing work on Local or any reachable route. Previously seen
+transitive nodes remain listed as offline with their last-seen time while a relay is down.
 
 ## Install & run
 
@@ -151,9 +160,10 @@ npm install -g @mmmbuto/nexuscrew
 nexuscrew
 ```
 
-The first run creates a loopback-only configuration and a `systemd --user` service when
-systemd is available. Linux x64 and ARM64 use platform PTY prebuilds; `node-pty` remains the
-build-from-source fallback.
+The first run creates a loopback-only configuration and starts a detached process. Run
+`nexuscrew boot` only if you want a persistent `systemd --user` service. Linux x64 and ARM64
+use platform PTY prebuilds only, so global installs do not compile native code or
+require install-script approval.
 
 ### macOS (Apple Silicon or Intel)
 
@@ -163,9 +173,10 @@ npm install -g @mmmbuto/nexuscrew
 nexuscrew
 ```
 
-The first run installs a user LaunchAgent with an explicit Node/Homebrew PATH. The npm package
-selects the matching Darwin ARM64 or x64 PTY prebuild. NexusCrew is an npm/Node CLI, not an
-`.app`, `.pkg`, or standalone Mach-O distribution, so it does not require Developer ID signing.
+The first run starts a detached process. Run `nexuscrew boot` to install a user LaunchAgent
+with an explicit Node/Homebrew PATH. The npm package selects the matching Darwin ARM64 or x64
+PTY prebuild. NexusCrew is an npm/Node CLI, not an `.app`, `.pkg`, or standalone Mach-O
+distribution, so it does not require Developer ID signing.
 
 ### Android / Termux (ARM64)
 
@@ -177,14 +188,18 @@ nexuscrew
 ```
 
 Termux uses the Android ARM64 PTY provider. The normal command starts NexusCrew in the
-background and exits, so it can also be used directly as a Termux:Boot startup command.
+background and exits. `nexuscrew boot` installs the Termux:Boot script explicitly.
 
 On every platform the first run starts the server in the background and opens the PWA wizard.
-After onboarding, the same command starts or reuses the background service and exits silently:
+After onboarding, the same command starts or reuses it, prints a compact status and guide, and
+exits:
 
 ```bash
 nexuscrew                 # background start; opens only on first run
 nexuscrew show            # background start when needed + open the authenticated PWA
+nexuscrew show token      # print the clickable authenticated URL; do not open a browser
+nexuscrew boot            # opt in to startup persistence
+nexuscrew boot off        # disable startup persistence, keep the current run alive
 ```
 
 The preferred port is `41820`. If it is occupied by another process, NexusCrew selects the
@@ -201,6 +216,8 @@ resolved PTY provider at startup.
 ```
 nexuscrew          background start; first run opens the PWA wizard
 nexuscrew show     start when needed and open the authenticated PWA
+nexuscrew show token  print the clickable authenticated URL without opening it
+nexuscrew boot     enable startup at boot (`boot off|status` are also available)
 nexuscrew doctor   local diagnostics (exit 1 when a required check fails)
 nexuscrew help     concise command help
 nexuscrew version  installed version
@@ -249,6 +266,10 @@ args = ["mcp"]
 The awkward tmux gestures, as buttons: **scroll** (enters copy-mode; then PgUp/↑/↓, `q` to
 exit), **window** prev/next, **pane** left/right, **esc**, **Ctrl-C**, **detach**.
 
+Long-press terminal text to enter local selection mode, then drag and use **Copy**. The
+composer send button writes the text followed by a real Enter while retaining textarea focus,
+so the mobile keyboard stays open between messages.
+
 Window and pane navigation run as **server-side, allowlisted tmux commands** on the active
 session — they are *not* emulated with client-side prefix keys, which are fragile and depend
 on each host's key bindings.
@@ -271,7 +292,7 @@ node bin/nexuscrew.js serve
 
 ## Status
 
-The current stable release is **v0.8.2**, published on npm under the **`latest`** dist-tag.
+The current stable release is **v0.8.4**, published on npm under the **`latest`** dist-tag.
 
 ## License