@wnzzer/agentdock 0.1.1 → 0.1.3

package/README.md

@@ -6,9 +6,15 @@ A host-native workspace for official Claude Code / Codex clients, built with Rus
 
 ```sh
 npm i -g @wnzzer/agentdock   # or: npx @wnzzer/agentdock
-agentdock
+agentdock                    # starts in the background and prints its URL
 ```
 
+`agentdock` runs as a gateway: it starts a detached server, waits until that
+server actually answers, and returns to the shell. `agentdock stop`, `restart`,
+`status` and `logs` manage it; `agentdock serve` runs in the foreground instead,
+which is what a supervisor such as systemd should use. A failed start prints the
+reason from the log and exits non-zero rather than leaving a silent process.
+
 One prebuilt binary per platform, carrying the Web client and the native bridge inside it. npm fetches only the one matching this machine, through `os`/`cpu` on its optional dependencies; there is no postinstall step, so `--ignore-scripts` installs work. Prebuilt for macOS (arm64, x64) and Linux (x64, arm64, static musl). Other platforms build from source below.
 
 Node is a requirement rather than an extra: the native-history and conversation bridges run as Node subprocesses, and Claude Code and Codex are themselves installed from npm.
@@ -25,7 +31,7 @@ pnpm run build:web
 cargo run -p agentdock-server
 ```
 
-Open **http://127.0.0.1:8787/**. The Rust server serves the built Web client and API on the same origin.
+Open **http://127.0.0.1:28789/**. The Rust server serves the built Web client and API on the same origin.
 
 For development, run `pnpm run dev` to start Cargo + Vite, then open **http://127.0.0.1:5173/**. If Rust is already running, use only `pnpm run dev:web`. Vite proxies `/api` and WebSockets to Rust. pnpm manages the workspace and dependencies; Vite, Vue SFC typechecking, tests and the native-history bridge run under Node. Rust builds still use Cargo.
 
@@ -130,7 +136,7 @@ SQLite schema 6 adds explicit environment maps with empty defaults, preserving o
 AGENTDOCK_DB                  # optional database path
 AGENTDOCK_HOME                # installation/state home; default ~/.agentdock for new installs
 AGENTDOCK_STATE_DIR           # optional persistent state directory
-AGENTDOCK_ADDR                # default 127.0.0.1:8787
+AGENTDOCK_ADDR                # default 127.0.0.1:28789
 AGENTDOCK_WEB_DIR             # state-dir/web if installed, else source apps/web/dist
 AGENTDOCK_NATIVE_BRIDGE       # optional path to packages/native-bridge/history.mjs
 AGENTDOCK_JS_RUNTIME          # native helper/chat/account runtime; default node (absolute path supported)
@@ -149,9 +155,26 @@ AGENTDOCK_INSTANCE_LABEL      # optional UI label for isolated preview deploymen
 
 ## Private remote access
 
-Simplest: keep loopback binding and use SSH port forwarding, `ssh -L 8787:127.0.0.1:8787 user@server`.
+```sh
+agentdock --lan
+```
 
-For a network bind, configure `AGENTDOCK_TOKEN` (24+ random characters), `AGENTDOCK_ALLOWED_ORIGINS=https://your-host`, and an HTTPS reverse proxy that preserves Host and WebSocket upgrades. Then sign in using the token in the Web UI. Do not expose this trusted-host workspace to untrusted users.
+Binds every interface, generates an access token if `AGENTDOCK_TOKEN` does not
+provide one, and prints it; `agentdock status` prints it again. The token is
+kept in the state directory, readable only by its owner — a background gateway
+cannot show it to you any other way, and deleting the file issues a new one.
+
+Reaching the machine at its own address needs nothing further: a `Host` that is
+an IP literal on the bound port is answered for, because DNS rebinding requires
+a *name* and cannot produce one. `AGENTDOCK_ALLOWED_ORIGINS` remains for the
+hostnames a reverse proxy serves under. Cross-site requests stay blocked by the
+Origin and `sec-fetch-site` checks either way.
+
+Traffic is plain HTTP, so on a network you do not control, prefer SSH port
+forwarding — `ssh -L 28789:127.0.0.1:28789 user@server` — or put an HTTPS
+reverse proxy in front that preserves Host and WebSocket upgrades. Do not expose
+this trusted-host workspace to untrusted users: whoever holds the token can run
+agents, read and write files, and open terminals on that machine.
 
 ## Boundaries
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wnzzer/agentdock",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Remote multi-agent development workspace for the official Claude Code and Codex CLIs",
   "license": "MIT",
   "homepage": "https://github.com/wnzzer/agentdock",
@@ -22,10 +22,10 @@
     "agentdock": "bin/agentdock.js"
   },
   "optionalDependencies": {
-    "@wnzzer/agentdock-darwin-arm64": "0.1.1",
-    "@wnzzer/agentdock-darwin-x64": "0.1.1",
-    "@wnzzer/agentdock-linux-x64": "0.1.1",
-    "@wnzzer/agentdock-linux-arm64": "0.1.1"
+    "@wnzzer/agentdock-darwin-arm64": "0.1.3",
+    "@wnzzer/agentdock-darwin-x64": "0.1.3",
+    "@wnzzer/agentdock-linux-x64": "0.1.3",
+    "@wnzzer/agentdock-linux-arm64": "0.1.3"
   },
   "files": [
     "bin/",