Agent Architecture

Kilo CLI

Kilo CLI is the terminal surface of Kilo Code 1.0, built from the kilocode repository and documented as sharing underlying technology with the IDE extensions while exposing MCP, ACP, agents, sessions, remote relay, plugins, permissions, config, and local reviews.

Source reviewed #11Checked 2026-07-06

Setup guide Source

Run type

CLI

Adapter

ts-plugin

Source

OSS · Kilo-Org/kilocode

Stars

★ 27k

Archive Context

This page is one host entry inside the full architecture archive and keeps multi-surface products visible instead of collapsing them into a single run type.

42 host archive

Host page

kilo-cli

Run cohort

CLI: 30

Archive route

/agents

Host Surface Perspectives

The host is the primary architecture boundary. Each runnable surface below separates what the host owns from what agent-connector can safely install for Kilo CLI.

1 surface entry

CLI

cli

Host entry: A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.
Host owns: The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.
Connector role: agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Implementation consequence: A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. No visible host-native gap is currently tracked for this surface.

Verified Architecture

Source-checked on 2026-07-06. These notes are intentionally separate from the generated surface matrix below.

Sequence #11

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

Kilo CLI shares source lineage with Kilo Code but is a separate adapter id, so the architecture must not collapse CLI and extension rows together.
The CLI row inherits the ts-plugin bridge expectations from the Kilo family while keeping entry point and install target separate from the IDE extension.
Marketplace and plugin statements must be scoped by adapter id because Kilo Code and Kilo CLI expose related but not identical host surfaces.

Runtime boundary

The adapter target is the `kilo` CLI/TUI, not the Kilo VS Code or JetBrains extension row. Kilo CLI owns terminal navigation, provider credentials, sessions, daemon/server modes, remote relay, and GitHub commands.

Install uses `npm install -g @kilocode/cli` or platform release binaries.
The docs say the CLI uses the same underlying technology as IDE extensions, but storage still needs CLI-specific handling.

MCP registration

Kilo CLI has explicit MCP commands and config: `kilo mcp`, `/mcps`, and `mcp` entries in `kilo.jsonc`. This should be documented as a terminal-native MCP surface.

Global config is `~/.config/kilo/kilo.json[c]` with project config in `./kilo.json[c]` or `./.kilo/`.
Kilo can also start an ACP server with `kilo acp`.

Hook bridge

Kilo CLI is a TypeScript-plugin style host in the connector matrix, but public CLI docs emphasize plugins, permissions, and command surfaces. Hook event claims should stay tied to adapter bridge behavior and source tests.

`kilo plugin <module>` installs a plugin and updates config.
Permission rules can allow, ask, or deny tools globally or with granular patterns.

Content surfaces

Kilo CLI content surfaces include agent modes, Agent Skills, custom agents, AGENTS.md initialization, sessions, review commands, model/provider config, TUI config, attention notifications, and external-directory permissions.

Built-in modes include Architect, Ask, Debug, Orchestrator, and custom modes.
`/review` supports local code review of staged, unstaged, branches, commits, and PRs.

Marketplace and host-only affordances

The host-only affordance is the CLI as an OpenCode-lineage, multi-model, MCP/ACP/plugin-capable terminal agent that also connects to Kilo Gateway, Cloud Agent, and Console surfaces.

Kilo CLI should be separate from the Kilo extension row even when technologies overlap.
Remote relay and gateway profile features may require account state.

Host-specific shape

Kilo CLI is an OpenCode-lineage ts-plugin host with all six core content/runtime surfaces wired and a local npm marketplace driver.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Visible gaps: none.

Hooks

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

Runtime handlers: none.
User-visible affordances: Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

Do not assume Kilo CLI and IDE extension storage are identical.
OpenCode lineage should not replace Kilo-specific verification.
Plugin and hook behavior need adapter-level tests before event details expand.

Evidence checked

Kilo CLI docs Kilo Code repository

Architecture Diagram

Host-specific flow for the CLI surface.

ts-plugin

1
Entry point: CLI
Terminal agent process reads user/project config and invokes the connector home binary for runtime callbacks.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: kilo-cli
ts-plugin renderer at src/adapters/kilo-cli/index.ts.
4
Native host artifacts
Adapter writes MCP config + plugin module + content files + memory/rules + marketplace bundle through this host's native file, package, or marketplace surface.
5
Runtime boundary
host loads generated TypeScript plugin bridge
6
User-visible surface
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
6/6 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

Static parts of the Kilo CLI integration and which side owns each one.

Kilo CLI host
CLI surface owns the model loop, UI shell, config discovery, and native lifecycle for this integration.
agent-connector package
Normalizes connector declarations into MCP, hook, memory, content, and action payloads before delegating to a host adapter.
kilo-cli adapter
Implements the ts-plugin translation layer in src/adapters/kilo-cli/index.ts.
Native artifacts
Adapter writes MCP config + plugin module + content files + memory/rules + marketplace bundle through this host's native file, package, or marketplace surface.
Runtime bridge
host loads generated TypeScript plugin bridge
User-visible surface
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the CLI surface.

1 · User / project
Choose host adapter
Install or update starts against Kilo CLI; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the kilo-cli adapter instead of exposing a generic host contract.
3 · kilo-cli adapter
Render host-native shape
Adapter writes MCP config + plugin module + content files + memory/rules + marketplace bundle through this host's native file, package, or marketplace surface.
4 · Kilo CLI
Host loads artifacts
host loads generated TypeScript plugin bridge
5 · Agent runtime
Run through host boundary
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
6/6 native surfaces wired. No visible host-native gap in the current coverage matrix.

Architecture Archive

The same five study axes are rendered for every host: runtime shape, hooks, MCP, memory, and host-only affordances.

Host-specific shape

Kilo CLI is an OpenCode-lineage ts-plugin host with all six core content/runtime surfaces wired and a local npm marketplace driver.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Visible gaps: none.

Hooks

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

Runtime handlers: none.
User-visible affordances: Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Special Feature Inventory

Host-specific capabilities separated from the generic surface matrix: lifecycle hooks, MCP registration, memory/rules, marketplace delivery, and UI or content affordances owned by the host.

Lifecycle hooks

Wired

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP registration

Wired

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory and rules

Wired

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace delivery

Driver wired

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

Host-only affordances

3/3 wired

Wired host affordances: Commands, Skills, Subagents. Host-native gaps: none. Not confirmed: Statusline handler, Action affordances.

Source Review Notes

Latest source pass for host-specific architecture details. This is separate from generated adapter coverage and local drift guards.

Checked 2026-07-06Open review source

Kilo-Org/kilocode repository

Kilo CLI shares source lineage with Kilo Code but is a separate adapter id, so the architecture must not collapse CLI and extension rows together.
The CLI row inherits the ts-plugin bridge expectations from the Kilo family while keeping entry point and install target separate from the IDE extension.
Marketplace and plugin statements must be scoped by adapter id because Kilo Code and Kilo CLI expose related but not identical host surfaces.

Evidence Map

Each host page ties public source evidence to the local adapter and drift guards that keep the rendered archive aligned with code.

Public source: Kilo-Org/kilocode

Primary public repository or product source used for current host status and source links.

external

Open source

Local adapter implementation

Defines the install/uninstall behavior, native config rendering, capability flags, and any runtime parse/format bridge for this host.

local

src/adapters/kilo-cli/index.ts

Platform metadata and host-native matrix

Records the form factor, public source target, ranking source, native host surfaces, and current agent-connector coverage cells.

local

site/src/platform-data.ts

Architecture drift guard

Asserts that every registered host has a page, diagram, host-specific brief, source link, form-factor band, and adapter-aligned surface data.

local

tests/docs/platform-drift.test.ts

Marketplace driver registry

Shows this host has a drivable package/plugin install path beyond direct native-file writes.

local

src/core/marketplace-drivers/registry.ts

Runtime Shape

The host loads a generated TypeScript plugin module that bridges in-process host events to the connector runtime.

MCP registration: Wired through this adapter
Hook bridge: Wired

Connector Surfaces

Static content

MCP server, Hooks, Commands, Skills, Subagents, Memory

Runtime handlers

No runtime handler surfaces wired

Surface Matrix

Wired means agent-connector installs it now. Host native marks support we know about but have not wired yet.

SurfaceStatus

MCP server

Static content