ML.

Coding-agent

Analyzing Cline: How Does a Coding Agent That Lives in Your Editor Detach Its Core From the Host?

Cline is a coding agent that lets you approve every action inside VS Code and roll back at any time. It also detaches its core from the host via a protobuf/gRPC boundary (ProtoBus + HostBridge), so the same core runs in the editor and in a terminal CLI. We analyze Plan/Act approval, checkpoints, and the host abstraction, contrasting them with OpenCode's headless engine.

Analyzing OpenCode: What Does a Coding Agent Look Like When You Make It a Provider-Agnostic Headless Engine?

OpenCode externalizes model metadata to models.dev and even hand-rolls its own LLM protocol layer, so any provider attaches with a single line of data. A single Effect-based HTTP engine is shared by the TUI, web, desktop, Slack, and editors (ACP), while two generations — legacy and V2 — coexist. We analyze the structure against Qwen Code's single-vendor platform.

CodeGraph Architecture Analysis: How Is the Code Intelligence Layer Beneath Coding Agents Built?

CodeGraph is a TypeScript tool that uses tree-sitter to parse source code, builds a local SQLite knowledge graph of symbols, edges, and files (with FTS5), and exposes that graph via an MCP server to coding agents like Claude Code, Cursor, Codex, and Hermes Agent. Instead of burning tokens navigating a codebase with grep/Read calls, agents get answers from a single codegraph_explore invocation. This post analyzes the architecture that makes that possible.

Analyzing Qwen Code: How Far Has a Terminal Coding Agent Become a Platform?

Qwen Code is a TypeScript-based coding agent that bundles a terminal CLI, an LLM provider abstraction, a tool scheduler, MCP, Skills, Subagents, the qwen serve daemon, channel plugins, and IDE integration into a single repository. We analyze how it reconstructs a Claude Code-style experience on top of Qwen/DashScope, multiple providers, and an extensible agent runtime.