@kynver-app/runtime 0.2.148 → 0.2.150

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.
Files changed (11) hide show
  1. package/README.md +2 -0
  2. package/dist/cli.js +226 -216
  3. package/dist/daemon-tick-thread.js +53 -51
  4. package/dist/desktop-entry.js +168 -164
  5. package/dist/index.js +243 -233
  6. package/dist/local-run-store/index.js +11 -10
  7. package/dist/server/dispatch-routing.js +4 -4
  8. package/dist/server/model-routing.js +4 -4
  9. package/dist/server/orchestration.js +2 -2
  10. package/dist/server/worker-policy.js +3 -3
  11. package/package.json +1 -1
package/README.md CHANGED
@@ -102,6 +102,8 @@ When website chat uses the browser on your computer, Kynver picks one automatica
102
102
 
103
103
  ## Agent tabs (Hermes, OpenClaw, Claude Code, Grok Bot)
104
104
 
105
+ Connect a coding agent (Claude Code, Codex, Cursor, OpenCode, Hermes) to your workspace with the one line from Kynver: `npx -y @kynver-app/connect@1 <CODE>` (or `kynver connect <CODE>`). Each agent's MCP entry then runs `kynver mcp serve --workspace <id>`, which reads that connection's key from your OS keychain and serves the `kynver_*` tools over stdio; no key is written into any agent config. `kynver mcp serve --check` says whether this computer is ready. `kynver connect --uninstall` removes what the line added and disconnects it.
106
+
105
107
  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).
106
108
 
107
109
  **One Hermes brain for Telegram and the tab.** `kynver tab adopt-hermes-session --conversation <Main id> --session <Telegram session id>` makes that tab conversation continue the Hermes session you talk to on Telegram (find the id with `hermes sessions list`). The daemon then follows the chat's session when Hermes rotates it, and holds a tab message for up to 10 minutes while a Telegram reply is still running in the same session (`KYNVER_HERMES_ADOPT_HOLD=off` turns the wait off). `--status` lists what is shared; `--release` stops following. It changes only `~/.kynver/agent-tab-sessions.json` and `~/.kynver/hermes-session-adoptions.json`, never Hermes' own config.