包含内容: - 应用程序: temp-auto-editor (带货短视频自动化剪辑系统) - 项目: auto-editor, FableCut, footage_screener - 文档: 视频工作流, chatcut, latentdync - 配置: config.toml, .env - 技能: kimi-webbridge - MCP 包装器: gitea wrapper.js - 记忆文件: memories/*.md - 会话摘要: session_index.jsonl 备份日期: 2026-07-27 14:00:28
1.9 KiB
Operations: daemon lifecycle and recovery
Read this only when a tool call can't reach the daemon, or the user explicitly asks to install / start / troubleshoot kimi-webbridge.
The daemon
The kimi-webbridge binary lives at ~/.kimi-webbridge/bin/kimi-webbridge (Windows: %USERPROFILE%\.kimi-webbridge\bin\kimi-webbridge.exe) and serves a local HTTP daemon on 127.0.0.1:10086. Status, PID, and logs live under ~/.kimi-webbridge/.
Recovery — what to do when a tool call fails
-
Daemon not reachable (connection refused) → start it yourself, don't ask the user.
startis idempotent: it no-ops if the daemon is already up, and concurrent starts converge to a single daemon (the OS lets only one process bind port 10086).- macOS / Linux:
~/.kimi-webbridge/bin/kimi-webbridge start - Windows:
& "$env:USERPROFILE\.kimi-webbridge\bin\kimi-webbridge.exe" start
Then retry the tool call.
- macOS / Linux:
-
command not found/ binary missing → not installed. Point the user to the help page below to install it. -
Extension won't connect, or anything still broken after a
start+ retry → don't deep-troubleshoot. Point the user to the help page:
Do NOT do automatically
Never run stop / restart / uninstall on your own. They kill the running daemon; if the user runs the Kimi Desktop App (which manages its own daemon), an external stop/restart also fights the app. If a hard restart is genuinely needed, ask the user to do it themselves — reopen the Kimi Desktop App, or run kimi-webbridge restart by hand.
/status JSON fields
running(bool) — daemon listening on:10086version(string) — daemon build versionextension_connected(bool) — a WebSocket client (the browser extension) is attachedextension_id(string) — the Chrome/Edge extension ID, empty if noneuptime_seconds(int)