Fetching from the wire…
Top 5 · 2026-05-14 · source-backed
Cline released @cline/sdk on May 13, an open-source TypeScript agent runtime that powers their CLI, VS Code, and JetBrains extensions. Running claude-opus-4.7, Cline CLI scores 74.2% on Terminal-Bench 2.0. Claude Code on the same model: 69.4%.
Same model. Different harness. Almost five percentage points of difference.
This validates everything the Claude Code teardown paper found. The harness matters more than the model. Cline's layered architecture splits into four packages: @cline/shared (types and utilities), @cline/llms (provider abstraction), @cline/agents (agent logic), and @cline/core (orchestration). Hub-backed persistent sessions mean your agent state survives across restarts, and cron automations let agents run on schedules without human initiation.
The competitive dynamics here are shifting fast. A year ago, the assumption was that the company that builds the model owns the agent experience. Cline just demonstrated that an open-source harness can beat the model maker's own agent on the model maker's own model. That changes the calculus for everyone building on top of these APIs.
I use Claude Code every day in my personal projects, and I'm not switching tomorrow. But I am paying close attention to what Cline's architecture enables. Hub-backed sessions and cron automations are features I'd love to have natively. The persistent session problem, where your agent loses all context when the process restarts, is one of the biggest friction points in my daily workflow.
The broader trend is clear too. Look at what else is happening simultaneously: OpenClaude hit 26K stars (Claude Code fork supporting 200+ models), Kilo Code claims 1.5M users and 25 trillion tokens processed, and DeepSeek-TUI gained 16K stars this week alone. The agent tooling layer is commoditizing in real-time. Your competitive advantage isn't "which agent CLI" anymore. It's your workflow design, context management, and model routing strategy.
Each link below shares sources, entities, or timing with this story.
openclaude uses DeepSeek / Shared entities / Same source domain / Shared topic / Tension
Linked by a graph relationship (openclaude uses DeepSeek); both cover Claude Code, Cline, DeepSeek, OpenClaude; reported by the same outlet (github.com).
Kilo Code supports JetBrains / Shared entities / Same source / Shared topic / What happened next / Tension
Linked by a graph relationship (Kilo Code supports JetBrains); both cover CLI, JetBrains, Kilo, Kilo Code; cite the same source (Kilo Code).
Vercel uses DeepSeek / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Vercel uses DeepSeek); both cover CLI, JetBrains, Kilo, Kilo Code; overlapping topics (agent, code).
openclaude built by Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (openclaude built by Claude Code); both cover APIs, Claude Code, Cline, VS Code; reported by the same outlet (github.com).
openclaude built by Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (openclaude built by Claude Code); both cover Claude Code, CLI, TUI, TypeScript; reported by the same outlet (github.com).
openclaude uses OpenAI / Shared entities / Shared topic / What happened next
Linked by a graph relationship (openclaude uses OpenAI); both cover Claude Code, CLI, Running, Same; overlapping topics (agent, architecture, claude, code, model).
openclaude uses OpenAI / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (openclaude uses OpenAI); both cover Claude Code, CLI, TypeScript, VS Code; reported by the same outlet (github.com).
openclaude uses DeepSeek / Shared entities / Shared topic / What happened next
Linked by a graph relationship (openclaude uses DeepSeek); both cover APIs, Bench, Claude Code, DeepSeek; overlapping topics (claude, code, model).