Agent Architecture

Cline

Cline is an editor-extension-centered agent row in agent-connector, even though the public project now also describes SDK and CLI assistant surfaces. Its integration shape is MCP and content oriented, with plugin/SDK lifecycle hooks treated as adjacent evidence rather than a wired extension hook surface.

Source reviewed #15Checked 2026-07-06

Setup guide Source

Run type

Extension

Adapter

mcp-only

Source

OSS · cline/cline

Stars

★ 68k

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

cline

Run cohort

Extension: 4

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 Cline.

1 surface entry

Extension

extension

Host entry: An IDE extension host runs inside VS Code, JetBrains, or another editor and receives workspace/editor context through that host's extension APIs.
Host owns: The editor owns activation, command palette placement, sidebar/chat UI, extension storage, trust prompts, and workspace permission boundaries.
Connector role: agent-connector targets documented extension-readable config, MCP, commands, skills, rules, and memory files without claiming control of the IDE. Current wired connector surfaces: MCP server, Commands, Skills, Memory.
Implementation consequence: Extension surfaces must distinguish file-backed connector artifacts from UI affordances that only the editor or marketplace extension can expose. 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 #15

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.

The repository describes Cline as an autonomous coding agent available as SDK, IDE extension, or CLI assistant, but this adapter row targets the IDE extension surface.
The repo exposes .cline and .clinerules content paths in its root, supporting the page's model of extension storage plus workspace rules/workflows/skills.
No lifecycle hook bridge is claimed for this row; it stays mcp-only from agent-connector's runtime perspective.

Runtime boundary

The adapter target remains the IDE extension surface. VS Code owns activation, UI state, workspace trust, extension storage, and the agent panel; agent-connector writes MCP and content artifacts without claiming control of Cline's full SDK or CLI assistant runtime.

The public repository describes Cline as an autonomous coding agent available as SDK, IDE extension, or CLI assistant.
The archive intentionally keeps this row in the extension band because that is the current adapter target.

MCP registration

Cline treats MCP servers as an extension mechanism for external databases, APIs, cloud infrastructure, and custom tools. agent-connector should therefore model MCP as a first-class extension host surface, not as a fallback.

The public README points to community servers and custom on-the-fly tool creation.
The CLI can manage servers with `cline mcp`, but this adapter row should not imply the VS Code extension and CLI share the same writable path unless verified.

Hook bridge

Cline's SDK/plugin text mentions lifecycle hooks programmatically, but the current agent-connector row is mcp-only from a runtime perspective. That distinction should stay visible so SDK-level hooks are not mistaken for a wired extension-host hook file.

Programmatic plugin hooks are useful architecture evidence for future SDK support.
No file-authored extension lifecycle hook bridge is promoted by this page without an adapter path and runtime contract.

Content surfaces

Cline content is extension/workspace oriented: rules, workflows, skills, and command-like content belong to the editor context rather than a terminal-only dot directory.

The adapter should keep global extension storage separate from project files.
Rules and skills are memory/content surfaces; they do not prove lifecycle interception.

Marketplace and host-only affordances

Cline's public architecture now includes plugins, MCP servers, multi-agent teams, scheduled agents, and messaging integrations. These are host-only orchestration affordances unless agent-connector has a byte-confirmed writable contract for them.

Multi-agent teams and scheduled agents are product capabilities, not the same as agent-connector subagent files.
Slack, Telegram, Discord, Google Chat, WhatsApp, and Linear integrations should be represented as host orchestration context rather than MCP by default.

Host-specific shape

Cline is a VS Code extension host centered on extension global storage plus workspace rules/workflows/skills; it is mcp-only from agent-connector's runtime perspective.

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

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

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

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

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

Known Limits

Do not collapse Cline's SDK, CLI assistant, and IDE extension into one adapter target.
SDK plugin lifecycle hooks are not treated as wired extension hooks in the current coverage matrix.
Future expansion should verify exact extension storage and workspace file paths before promoting host-native gaps.

Evidence checked

cline/cline repository

Architecture Diagram

Host-specific flow for the Extension surface.

mcp-only

1
Entry point: Extension
IDE extension host reads extension global storage and workspace-scoped files while the editor owns activation and UI.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: cline
mcp-only renderer at src/adapters/cline/index.ts.
4
Native host artifacts
Adapter writes MCP config + content files + memory/rules through this host's native file, package, or marketplace surface.
5
Runtime boundary
host calls MCP tools through its client
6
User-visible surface
Users see managed commands + skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
4/4 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

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

Cline host
Extension 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.
cline adapter
Implements the mcp-only translation layer in src/adapters/cline/index.ts.
Native artifacts
Adapter writes MCP config + content files + memory/rules through this host's native file, package, or marketplace surface.
Runtime bridge
host calls MCP tools through its client
User-visible surface
Users see managed commands + skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the Extension surface.

1 · User / project
Choose host adapter
Install or update starts against Cline; the selected surface is Extension.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the cline adapter instead of exposing a generic host contract.
3 · cline adapter
Render host-native shape
Adapter writes MCP config + content files + memory/rules through this host's native file, package, or marketplace surface.
4 · Cline
Host loads artifacts
host calls MCP tools through its client
5 · Agent runtime
Run through host boundary
Users see managed commands + skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
4/4 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

Cline is a VS Code extension host centered on extension global storage plus workspace rules/workflows/skills; it is mcp-only from agent-connector's runtime perspective.

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

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

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

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Runtime handlers: none.
User-visible affordances: Users see managed commands + skills + 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

Not confirmed

No user-installable lifecycle hook boundary is confirmed for this host.

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

Direct files

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Host-only affordances

2/2 wired

Wired host affordances: Commands, Skills. Host-native gaps: none. Not confirmed: Subagents, 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

cline/cline repository

The repository describes Cline as an autonomous coding agent available as SDK, IDE extension, or CLI assistant, but this adapter row targets the IDE extension surface.
The repo exposes .cline and .clinerules content paths in its root, supporting the page's model of extension storage plus workspace rules/workflows/skills.
No lifecycle hook bridge is claimed for this row; it stays mcp-only from agent-connector's runtime perspective.

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: cline/cline

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/cline/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

Runtime Shape

The host accepts MCP registration, but has no confirmed hook bridge for agent-connector to call.

MCP registration: Wired through this adapter
Hook bridge: No confirmed hook surface

Connector Surfaces

Static content

MCP server, Commands, Skills, 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

agent-connector installs this surface today.

Wired

Hooks

Static content

No confirmed host-native surface.

N/A

Commands

Static content

agent-connector installs this surface today.

Wired

Skills

Static content

agent-connector installs this surface today.

Wired

Subagents

Static content

No confirmed host-native surface.

N/A

Memory

Static content

agent-connector installs this surface today.

Wired

Statusline handler

Runtime handler

No confirmed host-native surface.

N/A

Action affordances

Runtime handler

No confirmed host-native surface.

N/A