Architecture · Kandev · doc-inline · balanced

How Kandev runs agent work

The Go backend is the control plane. It owns persistence and provider access, then routes scoped control channels to local or remote agent runtimes.

How Kandev runs agent work A browser or Tauri window connects to the Go backend, which owns database and provider access and routes control channels to local and remote agentctl runtimes. Each runtime starts an agent CLI with task MCP. USER SURFACE CONTROL PLANE PERSISTENCE + TASK RUNTIMES HTTP + WEBSOCKET CONTROL CHANNEL CONTROL CHANNEL Browser / Tauri window HTTP + WebSocket Go backend orchestrator · control plane SQLite / PostgreSQL persistent state Git + provider APIs external systems agentctl: local worktree runtime agentctl: remote Docker / K8s / SSH / Sprites Agent CLI + task MCP local task execution Agent CLI + task MCP remote task execution INTERNAL ROUTE UI / CONTROL CHANNEL CONTROL PLANE FOCAL