kimi-bridge

Control a local Kimi Code agent from an instant-messaging conversation.

kimi-bridge supervises Kimi Code's local server, keeps chat-to-session bindings across restarts, streams editable replies, and brings approvals, questions, steering, files, thinking output, and session controls into your chat client.

Support

Only one adapter runs in each bridge process. Feishu uses the official lark-oapi WebSocket client. Telegram and QQ use small handwritten httpx/websockets transports without a platform SDK dependency.

Features

• Durable Kimi session creation, listing, switching, renaming, inspection, compaction, and undo.
• Edit-in-place answer streaming, router-side chunking, and optional separate thinking output.
• Interactive approvals and questions with timeout handling and stale-action protection.
• Busy-turn prompt steering, cancellation, permission modes, model/effort/plan controls, goals, tasks, skills, and read-only MCP inspection.
• Inbound images and files plus workspace-contained outbound /send.
• Private-chat allowlists, loopback-only Kimi server supervision, and a secret-safe non-starting doctor command.

Quick start

The easiest path: open any CLI agent and say — "Read https://github.com/Mtrya/kimi-bridge/blob/main/INSTALL_AI.md and help me configure kimi-bridge." The agent interviews you and runs the setup end to end.

Manual skeleton — requires authenticated Kimi Code and uv:

uv tool install 'kimi-bridge'     # install
# create ~/.kimi-bridge/config.toml for one adapter, chmod 600
kimi-bridge doctor                # validate without starting anything
kimi-bridge                       # run

Full walkthrough in INSTALL.md; complete adapter examples in the configuration reference.

Commands

Commands cover:

• sessions: /new, /sessions, /switch, /status, /title, /usage, /compact, /undo;
• control: /mode, /model, /effort, /plan, /goal, /stop;
• tasks and tools: /tasks, /skills, /mcp;
• output: /send, /render-thinking.

Use /help in chat or read the command reference for exact grammar, busy-session behavior, and platform media semantics. Send /<command> ? for detailed in-chat usage, including sub-forms such as /tasks show ?.

Architecture and security

Feishu, QQ, or experimental Telegram
              │
              ▼
       semantic chat router
              │
              ▼
  supervised local `kimi web`

The managed Kimi server binds to loopback with a generated bearer token, and chat access is restricted by the adapter's allowlist. kimi-bridge is designed for one trusted operator, not mutually untrusted tenants: a permitted Kimi agent can read, write, and execute with the host account's authority, so protect both the host and chat credentials. Component boundaries and the Kimi Code compatibility policy (kimi-bridge compat) live in Architecture.

Documentation

• Install and operate
• Agent-driven setup
• Configure
• Commands and interactions
• Architecture and compatibility
• Upstream Kimi Code
• Report an issue

Development

uv sync --dev
uv run pytest -q
uv run ruff check .

Unit tests use fake Kimi, Feishu, Telegram, QQ, WebSocket, state, and process boundaries; hosted checks use no credentials or inference.

License

MIT © 2026 Mtrya