@kynver-app/runtime 0.2.122 → 0.2.129

package/README.md

@@ -82,7 +82,7 @@ config ensure-default-repo
 doctor runner-install | node-runtime | local-store | context-envelope | runtime-takeover
 report-bug [--json] [--message TEXT] [--skip-doctor]
 browser status | install [--deps] [--force]
-agents status [--json] | setup hermes|openclaw|claude-code [--dry-run]
+agents status [--json] | setup hermes|openclaw|claude-code|grok-bot [--dry-run]
 ```
 
 Run `kynver help` for the full flag-level usage.
@@ -91,9 +91,9 @@ Run `kynver help` for the full flag-level usage.
 
 When website chat uses the browser on your computer, Kynver picks one automatically: a path you configured, then an installed Chrome / Chromium / Edge, then its own copy. If there is none, Kynver downloads Chrome for Testing (Google's official build, about 150 MB, once) into `~/.kynver/browsers` — no sudo. `kynver browser status` shows what will be used; `kynver browser install` downloads it now. On a minimal Linux or WSL install Chrome may also need system libraries: `kynver browser status` prints the exact `apt-get` / `dnf` command, and `kynver browser install --deps` runs it when sudo needs no password. On WSL the browser window appears on your Windows desktop through WSLg; without a display it runs headless. Turn the automatic download off with `"browserAutoProvision": false` in `~/.kynver/config.json`.
 
-## Agent tabs (Hermes, OpenClaw, Claude Code)
+## Agent tabs (Hermes, OpenClaw, Claude Code, Grok Bot)
 
-Kynver chat can open a tab for each agent you run on this computer: your Hermes Agent, your OpenClaw agent, or your own signed-in Claude Code. The daemon talks to them on localhost and relays messages over its existing Kynver connection — nothing is exposed to the internet and their keys never leave this computer. `kynver agents status` shows what was found. `kynver agents setup hermes` switches on Hermes's local API server in `~/.hermes/.env` (with a new local-only key); restart the Hermes gateway afterwards. `kynver agents setup openclaw` switches on the OpenClaw gateway's chat API and restarts it. Claude Code needs only `claude` signed in and a folder chosen for chat computer access. Steps are logged to `~/.kynver/logs/agent-tabs.jsonl` (no message text); session ids per tab live in `~/.kynver/agent-tab-sessions.json`. `KYNVER_OPENCLAW_AGENT` picks a non-default OpenClaw agent; `KYNVER_AGENT_TAB_CLAUDE_MODEL` pins a Claude Code model (default: your own Claude Code default).
+Kynver chat can open a tab for each agent you run on this computer: your Hermes Agent, your OpenClaw agent, your own signed-in Claude Code, or Grok Bot. The daemon talks to Hermes, OpenClaw and Claude Code on localhost and relays messages over its existing Kynver connection — nothing is exposed to the internet and their keys never leave this computer. `kynver agents status` shows what was found. `kynver agents setup hermes` switches on Hermes's local API server in `~/.hermes/.env` (with a new local-only key); restart the Hermes gateway afterwards. `kynver agents setup openclaw` switches on the OpenClaw gateway's chat API and restarts it. Claude Code needs only `claude` signed in and a folder chosen for chat computer access. Grok Bot is detected when the desktop app is installed (`grok-bot` on PATH, the Linux package, or the app's config directory). It has no published connection that accepts a message and returns the reply, so `kynver agents setup grok-bot` explains that and exits with an error. The Kynver tab keeps the name you set and does not deliver chat. Steps are logged to `~/.kynver/logs/agent-tabs.jsonl` (no message text); session ids per tab live in `~/.kynver/agent-tab-sessions.json`. `KYNVER_OPENCLAW_AGENT` picks a non-default OpenClaw agent; `KYNVER_AGENT_TAB_CLAUDE_MODEL` pins a Claude Code model (default: your own Claude Code default).
 
 ## Worker providers