lobstah 0.3.1 → 0.5.0

package/README.md

@@ -46,6 +46,20 @@ pnpm install && pnpm build
 ln -s "$PWD/bin/lobstah" /usr/local/bin/lobstah   # Windows: add .\bin to PATH
 ```
 
+No Node on the box? Standalone binaries (bun-compiled) ship with every
+[release](https://github.com/aequitas-labs/lobstah/releases) for
+macOS/Linux/Windows:
+
+```bash
+curl -fsSL -o /usr/local/bin/lobstah \
+  https://github.com/aequitas-labs/lobstah/releases/latest/download/lobstah-darwin-arm64
+chmod +x /usr/local/bin/lobstah
+```
+
+The binary drives harnesses through their CLIs instead of the bundled SDKs:
+codex workers run fully Node-free; claude workers still need the (Node-based)
+`claude` CLI on the host.
+
 ## Quick start 🪝
 
 ```bash
@@ -85,10 +99,10 @@ lobstah man tend                      # the whole string: fleet verdict, waiting
 lobstah watch add ci:1234 --check 'my-ci events --since {cursor} --json'
                                       # stand watch on anything external — its
                                       # events wake you like a dispatch would
-lobstah soak --session <id>           # volunteer a live interactive session as
-                                      # a worker: it parks at turn end and takes
-                                      # bait (`dispatch --for session:<id>`
-                                      # targets it) instead of a headless spawn
+lobstah soak                          # volunteer this worktree's session as a
+                                      # worker: sign-on anchors its wt:<trap>
+                                      # address; `dispatch --for wt:<trap>` bait
+                                      # waits for it, never a headless spawn
 ```
 
 Prefer the water? 🌊 `set --bait`, `buoys`, and `buoy` alias `dispatch`,
@@ -107,7 +121,10 @@ Set one config line — `notifyCommand = "ntfy pub my-topic ..."` — and the
 daemon pings you on `needs-decision`, `blocked`, `done`, and `failed`. No
 model in the loop. Driving lobstah from an agent session instead? `lobstah
 man` prints the lobsterman's manual. `man wait` blocks until a dispatch needs
-attention, and unanswered questions re-fire until answered. `man init`
+attention, and unanswered questions re-fire until answered. `man helm`
+signs one session on as the orchestrator for its grounds, and `man report`
+prints the delta since the last acknowledged report. `lobstah glass` serves
+it all as a live localhost page — the spyglass. `man init`
 installs a Claude Code Stop hook that parks the session on the fleet and
 continues the turn the moment something needs it.
 
@@ -134,7 +151,9 @@ continues the turn the moment something needs it.
   [docs/openclaw.md](https://github.com/aequitas-labs/lobstah/blob/main/docs/openclaw.md)
 - **The lobsterman** — one interactive agent session that dispatches,
   supervises, and hands you outcomes, woken by the `lobstah man` commands.
-  [docs/lobsterman.md](https://github.com/aequitas-labs/lobstah/blob/main/docs/lobsterman.md)
+  Harness-agnostic: hold the helm from Claude Code, Codex, or anything with
+  a terminal — the CLI is the contract, and workers mix harnesses per
+  dispatch. [docs/lobsterman.md](https://github.com/aequitas-labs/lobstah/blob/main/docs/lobsterman.md)
 
 ## How it holds together 🧭