@kynver-app/runtime 0.2.130 → 0.2.135

package/README.md

@@ -17,11 +17,16 @@ Standalone Kynver AgentOS execution runtime and CLI (`kynver`) — run Kynver's
 
 ```bash
 npm install -g @kynver-app/runtime
-kynver bootstrap --api-base-url https://www.kynver.com
-kynver start
+kynver
 ```
 
-That is the whole golden path: `bootstrap` links this machine to your account and workspace; `start` brings the agent online (keeper-supervised daemon — Ctrl-C stops it). For a persistent background agent on Linux: `kynver start --install-systemd`.
+That's it. The first time, `kynver` links this computer to your Kynver account: it opens the approval page in your browser (the link and code are printed too), you click approve, and it sets up this computer and brings Kynver online. After that, `kynver` just starts it. If Kynver is already running on this computer it says "Kynver is already running ✓" and does nothing else. `kynver stop` stops it.
+
+While it runs, the window stays calm: a short status block ("Kynver is online ✓ · linked to … · chat: Claude Code"), then one line per chat message it answers. Problems are printed in plain words with the command that fixes them. The full log is always in `~/.kynver/logs/kynver.log`; `kynver --verbose` (or `KYNVER_VERBOSE=1`) shows it in the window as well.
+
+**Website chat on this computer** turns on by itself when Claude Code (or Codex) is installed, and `kynver` says so once: "Website chat will use Claude Code on this computer. Turn off: kynver setup --no-chat-oauth". The choice is saved, so `kynver` and `kynver start` follow it with no flag.
+
+Other Kynver sites (staging, local dev): `kynver --api-base-url https://your-kynver-site`. For a persistent background agent on Linux: `kynver start --install-systemd`. The step-by-step commands (`kynver bootstrap`, `kynver setup`, `kynver start`, `kynver daemon --run …`) still work exactly as before.
 
 ### Windows: Kynver Desktop
 
@@ -29,7 +34,7 @@ On Windows x64 there is also **Kynver Desktop**, which bundles this runtime and
 install and no terminal. It is offered in **Account → Settings** (next to these commands) only once a release is
 published, and a scenario is declared supported only after it has been tested end to end; until then the command line
 above is the way in. Only one runtime may work for a workspace on a computer: quit Desktop before running
-`kynver start`, and stop the CLI before starting Desktop.
+`kynver`, and stop the CLI (`kynver stop`) before starting Desktop.
 
 ### What `kynver bootstrap` does
 
@@ -37,11 +42,11 @@ above is the way in. Only one runtime may work for a workspace on a computer: qu
 2. **Workspace resolution** — resolves your account's primary AgentOS workspace. If the account is not approved for Agentic OS yet, bootstrap says so and links the request page (see Requirements above).
 3. **Machine setup** — persists `~/.kynver/config.json` (API base URL, workspace id, repo discovery, worker caps, box identity) and mints a scoped `krc1.*` runner credential.
 
-Bootstrap does **not** start any work — bringing workers online is `kynver start`.
+Bootstrap does **not** start any work — bringing workers online is `kynver` (or `kynver start`). Bare `kynver` runs bootstrap for you on a computer that isn't linked yet.
 
 ### Troubleshooting → `kynver doctor runner-install`
 
-If `bootstrap` or `start` fails, or the agent seems dead:
+If `kynver` (or `bootstrap` / `start`) fails, or the agent seems dead:
 
 ```bash
 kynver doctor runner-install
@@ -74,7 +79,8 @@ Global env secrets are accepted on by-id callbacks **only** when the deployment
 ## CLI verbs
 
 ```text
-bootstrap | start | status | setup | login | daemon
+(no verb) — start Kynver (links this computer first if needed)
+stop | bootstrap | start | status | setup | login | daemon
 run create | list | status | dispatch | sweep
 worker start | status | tail | stop | complete
 runner credential [mint|status|list|revoke|rotate]