@openscout/scout 0.2.63 → 0.2.64

package/README.md

@@ -172,6 +172,28 @@ Aliases: `runtime:` = `harness:`, `persona:` = `profile:`, `branch:` / `worktree
 
 If direct send/ask still comes back unresolved, treat that as a routing problem, not a mere "target is offline" problem. The right follow-up is to disambiguate the target, inspect broker context with `scout who` / `scout latest`, or create/register the missing identity. Do not default to pushing the bring-up step back onto the operator for a known target.
 
+By default, a label handoff such as `@openscout.harness:claude` should mean
+"use the OpenScout identity on the Claude harness in a fresh session/context."
+Reusing an existing session is an explicit continuity choice, not the default.
+The broker should keep the stable agent name as the address and record the
+concrete session binding in the delivery receipt/history.
+
+Session refs are separate route targets for continuing a concrete bound
+session. Use the bare `ref:<suffix>` form in receipts/history, and pass the
+suffix with `--ref`; do not encode refs into `@agent#harness?model` identity
+syntax.
+
+```bash
+scout ask --ref 7f3a9c21 "continue from that handoff"
+scout send --ref 7f3a9c21 "status for that same session"
+```
+
+Receipts should name both layers, for example:
+
+```text
+sent to @openscout#claude via DM (ref:7f3a9c21)
+```
+
 ## Current Commands
 
 ```bash
@@ -227,10 +249,13 @@ scout server open
 scout server start
 scout server start --port 3200
 scout server open --path /agents/arc-codex-2.master.mini
+scout server start --public-origin https://scout.my-mac.local
 scout server start --vite-url http://127.0.0.1:43173   # SPA dev server
 scout server start --static --static-root /custom/client
 ```
 
 `scout server open` reuses an already-running matching Scout server on that port, or starts one in the background and opens the browser for you. Use `scout server` or `scout server help` for full flags.
 
+The application server derives the LAN hostname `scout.<machine>.local` by default. For a Caddy or other edge proxy, set `--public-origin https://scout.<machine>.local` (or `OPENSCOUT_WEB_PUBLIC_ORIGIN`) so browser origins match the app server's trusted host model.
+
 For the same web UI without the full `scout` CLI package, use **`@openscout/web`** (`openscout-web`): it ships its own `dist/client`, bundled Bun server, and pairing supervisor.