Editor embedding (ACP)

ka acp

ka acp speaks the Agent Client Protocol: JSON-RPC over stdio, the way editors embed agents. If your editor supports ACP (Zed and JetBrains via plugin, among others), point it at the ka binary and the agent appears in-editor.

Session resume

session/load accepts a strand id prefix, same as everywhere else: point the editor at an existing conversation and it replays over the protocol like ka serve does over SSE.

Why ACP

The engine’s Command/Event protocol maps cleanly onto ACP’s turn model, so ka acp is a thin adapter: one process per editor session, no daemon, no port. Everything else (clearances, hardstops, strands) behaves exactly as in the TUI.

Status

ACP support is young, like the rest of ka. If your editor’s ACP integration misbehaves, ka doctor and a TUI session on the same strand are the fastest way to see whether the issue is the adapter or the engine.