@kynver-app/runtime 0.2.129 → 0.2.130
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 +3 -0
- package/dist/cli.js +218 -207
- package/dist/desktop-entry.js +171 -160
- package/dist/index.js +242 -231
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -83,6 +83,7 @@ doctor runner-install | node-runtime | local-store | context-envelope | runtime-
|
|
|
83
83
|
report-bug [--json] [--message TEXT] [--skip-doctor]
|
|
84
84
|
browser status | install [--deps] [--force]
|
|
85
85
|
agents status [--json] | setup hermes|openclaw|claude-code|grok-bot [--dry-run]
|
|
86
|
+
tab post --conversation <id> [--file <path>]... [--key <k>] <text|-|@file>
|
|
86
87
|
```
|
|
87
88
|
|
|
88
89
|
Run `kynver help` for the full flag-level usage.
|
|
@@ -95,6 +96,8 @@ When website chat uses the browser on your computer, Kynver picks one automatica
|
|
|
95
96
|
|
|
96
97
|
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).
|
|
97
98
|
|
|
99
|
+
**Updates about work go to the chat that started it.** Each tab message tells the agent which Kynver conversation it is in: Hermes and OpenClaw get a line in the turn's system note (and an `X-Kynver-Conversation` header); Claude Code gets `KYNVER_CONVERSATION` (and `KYNVER_AGENT_TAB_ENGINE`) in its environment. When work started there finishes, fails, needs you or opens a PR, the agent posts back with `kynver tab post --conversation <id> "PR is green"` (`--file <path>` attaches files, big ones are uploaded first; `-` reads the text from stdin, `@notes.md` from a file; the same `--key` never posts twice). It defaults to `$KYNVER_CONVERSATION` and refuses with neither — it never falls back to whatever conversation is open. Kynver tasks created with `originConversationId` post their own finished / failed / needs-you / PR updates into that conversation automatically.
|
|
100
|
+
|
|
98
101
|
## Worker providers
|
|
99
102
|
|
|
100
103
|
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`.
|