Runtime & Integrations

Runtime and integrations

Embed Codewhale in the tools you already use. Beyond the terminal, it runs a local control plane that editors, scripts and chat apps can talk to.

Integration surfaces

HTTP / SSE Runtime APIFull local HTTP + Server-Sent Events runtime API on 127.0.0.1:7878. Create threads, stream turns, manage background jobs, and control approval decisions — all from any HTTP client or the bundled mobile page.
ACP (Agent Client Protocol)Baseline JSON-RPC adapter over stdio for compatible editor clients such as Zed. It supports initialize, new session, prompt, and cancel with text responses; shell and file tools, checkpoint replay, and session loading remain on the full Runtime API.
MCP (Model Context Protocol)Connect Codewhale to external tools and services through configured MCP servers over stdio or HTTP/SSE, or expose Codewhale's own tools to another MCP client.
VS Code ExtensionEarly companion for the local runtime. It can open Codewhale in a terminal, start and check the Runtime API, and show read-only thread summaries and restore points. It does not yet provide full chat, inline edits, or editor actions.
Telegram BridgeFirst-party Telegram bot bridge. Start a headless Codewhale session, then chat with it from any Telegram client — approvals, tool results, and completions surface inline.
Feishu / Lark BridgeFirst-party Feishu / Lark bot bridge. Chat-native agent loop inside your Feishu workspace with approval cards, session linking, and audit trail.
Weixin BridgeExperimental Weixin / WeChat bridge. Receive agent completions and approvals inside WeChat; early-stage and not recommended for production deployments.Experimental

Trust boundary

Runs on your machine

The Runtime API binds 127.0.0.1 by default. The local runtime does not require a Codewhale account or hosted relay.

Auth required

Runtime API routes (/v1/*) require a Bearer token. Pass --auth-token at startup or set CODEWHALE_RUNTIME_TOKEN. Only a loopback bind can turn this off, with --insecure-no-auth.

Permissions user-controlled

Remote clients submit requests and approval decisions through the authenticated Runtime API. Local mode, permission posture, and sandbox policy still apply.

Open protocols

The HTTP/SSE Runtime API, MCP surface, and baseline ACP stdio adapter serve different integration needs; choose the interface your compatible client supports.

Runtime facts

Version: 0.10.0
Tool count: 80
Sandbox backends: seatbelt (macOS, when available) · bubblewrap (Linux, opt-in when installed)

Details

Crates: 27 · agent, app-server, build-support, cli, cloud-facts, command-contract, config, core, execpolicy, hooks, lane, localization, mcp, memory, models, palette, paths, protocol, release, runtime, secrets, state, telemetry, tools, tui, workflow, workflow-js
Source revision: 24a7b99a73c186e70dfb8341b046d638f28d4cbb

Detailed implementation docs:Runtime API and ACP stdio adapter MCP integration