cline /

Cline

Live map
View repository
Snapshotmain · 8bbdde2

CLI and IDE hosts delegate durable sessions to Core, which drives a stateless model-and-tool loop.

Click a building or route
Choose a path

Start a session, call the model, edit the workspace, and persist the result.

System map8 components · 9 connections
130%
Cline: one agent engine, several hosts architectureEnter from a host, descend through Core and Agent Runtime, then fan out to providers, tools, and shared session state.prompt, workspace, mod…runtime config, messag…prepared messages and …tool names, arguments,…approved file, search,…assistant content, too…content deltas, tools,…CLI &IDE hostsCline CoreLLM providersAgent RuntimeTool routerSession & HubMCP & pluginsWorkspaceexecutors
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

CoreThe stateful orchestration layer shared by Cline host applications.

How to study this repo

  1. 1
    Read the layers

    Use sdk/ARCHITECTURE.md to establish package dependency direction.

  2. 2
    Follow a turn

    Trace a host prompt through Core, Agent Runtime, and the model provider.

  3. 3
    Route one tool

    Compare a built-in executor with an MCP-backed tool call.