@kynver-app/runtime 0.2.117 → 0.2.118
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -0
- package/dist/cli.js +190 -173
- package/dist/desktop-entry.js +145 -133
- package/dist/index.js +207 -190
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -82,6 +82,7 @@ config ensure-default-repo
|
|
|
82
82
|
doctor runner-install | node-runtime | local-store | context-envelope | runtime-takeover
|
|
83
83
|
report-bug [--json] [--message TEXT] [--skip-doctor]
|
|
84
84
|
browser status | install [--deps] [--force]
|
|
85
|
+
agents status [--json] | setup hermes|openclaw|claude-code [--dry-run]
|
|
85
86
|
```
|
|
86
87
|
|
|
87
88
|
Run `kynver help` for the full flag-level usage.
|
|
@@ -90,6 +91,10 @@ Run `kynver help` for the full flag-level usage.
|
|
|
90
91
|
|
|
91
92
|
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`.
|
|
92
93
|
|
|
94
|
+
## Agent tabs (Hermes, OpenClaw, Claude Code)
|
|
95
|
+
|
|
96
|
+
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).
|
|
97
|
+
|
|
93
98
|
## Worker providers
|
|
94
99
|
|
|
95
100
|
Set once in `kynver setup --provider claude|cursor|codex|gemini|gemini-api|openai-compatible` (stored in `~/.kynver/config.json` as `workerProvider`). `--provider chatgpt` / `gpt` are aliases for `codex`.
|