+++
title = "Cline SDK Released: The Open-Source Agent Runtime for AI Development"
date = 2026-05-24
draft = false
description = "Cline SDK 1.0.0 released. Introduction of the Cline SDK as an open-source agent runtime. The new foundation powering Cline's CLI and Kanban interfaces. Upgrade urgency: high."
slug = "cline-sdk-released-open-source-agent-runtime"
tags = ["cline sdk", "release", "version", "ai agents", "open-source"]
categories = ["Releases"]
author = "AI Expert"
showReadingTime = true
showTableOfContents = true
toc = true
+++

> ⚠️ **HIGH PRIORITY** — Important fixes and foundational changes. Upgrade soon.

> **Version:** 1.0.0 | **Released:** 2026-05-24 | **Upgrade from:** N/A (First Public Release of Cline SDK - fundamental re-architecture)

## Release at a Glance

The Cline team is excited to announce the **Cline SDK 1.0.0**, a major milestone establishing Cline as an open-source agent runtime for AI development. This release fundamentally re-architects how Cline operates, providing a robust, extensible foundation for building sophisticated agentic AI applications.

Here's the TL;DR for developers:

*   **New Open-Source Core:** Cline's capabilities are now powered by the `Cline SDK`, an open-source agent runtime.
*   **Unified Ecosystem:** Cline's CLI, Kanban, and IDE extensions have been rebuilt or migrated to leverage this new SDK, ensuring a consistent and powerful developer experience.
*   **Advanced AI Agent Features:** The SDK enables agents to understand project structure, make coordinated code changes, and automatically correct errors (syntax, types, imports).
*   **High Upgrade Urgency:** All developers currently using or planning to use Cline should prioritize upgrading to benefit from the new architecture and improved agent accuracy.

This release marks a significant step towards democratizing agentic AI development, providing the tools needed to create more intelligent and autonomous coding assistants.

## Headline New Features

The Cline SDK 1.0.0 introduces a suite of powerful capabilities designed to empower developers building the next generation of AI agents.

### The Cline SDK: Open-Source Agent Runtime

At its core, Cline SDK 1.0.0 is an open-source runtime specifically engineered for AI agents. It provides the foundational logic and APIs necessary for agents to interact with codebases, understand context, and execute complex tasks. This shift to an SDK-centric architecture means more transparency, extensibility, and community contribution opportunities.

### Unified Foundation for Cline's Ecosystem

The new SDK now underpins all of Cline's primary interfaces: the **CLI**, **Kanban**, and **IDE extensions**. This unification ensures that whether you're interacting with Cline through your terminal, a visual board, or directly within your editor, you're leveraging the same powerful and consistent agent runtime. This eliminates inconsistencies and streamlines development across tools.

### Advanced Code Editing Capabilities

One of the most impactful features of the new SDK is its enhanced ability to interact with and modify code. Agents powered by the Cline SDK can now:

*   **Read Project Structure:** Understand the hierarchical organization of files and directories within a project.
*   **Understand File Relationships:** Analyze dependencies and connections between different code files.
*   **Make Coordinated Changes:** Perform complex refactoring or feature implementations that require modifications across multiple files, ensuring consistency and correctness.

This capability moves beyond simple file edits, allowing agents to act as true collaborators on large projects.

```typescript
// Conceptual example: Using the SDK to define an agent's project interaction
import { AgentRuntime, ProjectContext, CodeChange } from '@cline/sdk';

class MyRefactoringAgent extends AgentRuntime {
  async run(context: ProjectContext): Promise<CodeChange[]> {
    const filesToRefactor = context.findFiles('src/**/*.ts');
    const changes: CodeChange[] = [];

    for (const file of filesToRefactor) {
      // Logic to analyze file content, identify patterns, and propose changes
      const updatedContent = await this.llm.refactorModule(file.content);
      changes.push({
        filePath: file.path,
        oldContent: file.content,
        newContent: updatedContent
      });
    }
    return changes;
  }
}

// The SDK handles applying these changes across the project context.

Automated Error Correction

The Cline SDK significantly enhances agent reliability by introducing automated error correction. Before completing a task, agents can now:

  • Identify Broken Syntax: Catch parsing errors in code.
  • Fix Type Mismatches: Correct type-related issues in statically typed languages.
  • Resolve Missing Imports: Automatically add necessary import statements.

This proactive error-fixing mechanism means agents deliver higher-quality code outputs, reducing the need for manual post-agent review and iteration.

// Conceptual example: SDK's internal error correction loop
// (Developer interacts with the high-level agent API, this happens under the hood)
async function executeAgentTask(task: AgentTask) {
  let codeOutput = await agent.generateCode(task.prompt);

  // SDK's built-in validation and correction loop
  let attempts = 0;
  while (hasErrors(codeOutput) && attempts < MAX_CORRECTION_ATTEMPTS) {
    const errors = analyzeErrors(codeOutput);
    codeOutput = await agent.correctCode(codeOutput, errors);
    attempts++;
  }

  if (hasErrors(codeOutput)) {
    throw new AgentCorrectionFailedError("Agent failed to auto-correct code.");
  }
  return codeOutput;
}

Breaking Changes and Removed APIs

This is a major release with foundational architectural changes. Developers should be aware of the following breaking changes, which will require updates to existing projects and integrations.

1. Deletion of Old CLI Source Tree

The previous cli/ source tree, which comprised approximately 9.5MB across 142 files, has been entirely removed. This includes the deletion of its associated references, such as the .clinerules/cli.md tribal knowledge file and the cli entry in package.json workspaces.

Impact: Any direct dependencies on the old CLI source code, internal modules, or invocation methods are now broken. The new Cline CLI is a separate package built on the SDK.

Before (Old CLI Usage Examples): If your project directly referenced the old CLI source or used its internal modules:

// package.json (BEFORE)
{
  "name": "my-cline-project",
  "workspaces": [
    "packages/*",
    "cli" // Direct dependency on the old CLI source tree
  ],
  "scripts": {
    "run-old-cli-feature": "node cli/src/main.js --feature"
  }
}
// old-project-script.js (BEFORE - Hypothetical direct import)
// This path no longer exists.
const oldCliCore = require('../../cli/src/core');
oldCliCore.performLegacyTask();
# Terminal command (BEFORE - Direct invocation of old CLI script)
node cli/src/main.js --check-syntax myFile.ts

After (New SDK & CLI Usage Examples): You must update your project to use the new @cline/sdk APIs or the newly re-architected @cline/cli package.

// package.json (AFTER)
{
  "name": "my-cline-project",
  "dependencies": {
    "@cline/sdk": "^1.0.0", // New SDK dependency
    "@cline/cli": "^1.0.0"  // New CLI if you need its commands
  },
  "scripts": {
    "run-new-cline-agent": "node my-agent-script.js", // Using the SDK
    "use-cline-cli": "cline --new-command"             // Using the new CLI package
  }
}
// new-project-script.js (AFTER - Using the new SDK)
import { AgentRuntime, ProjectContext } from '@cline/sdk';

class MyNewAgent extends AgentRuntime {
  async run(context: ProjectContext) {
    // ... use SDK APIs to interact with the project and agents
  }
}
// Example: Instantiating and running an agent
const myAgent = new MyNewAgent();
// myAgent.run(someProjectContext);
# Terminal command (AFTER - Using the new global/local CLI command)
cline --check-project-health

2. Migration of IDE Extensions

Cline’s official IDE extensions have been rebuilt and migrated to leverage the new SDK architecture.

Impact: If you maintained custom IDE extensions or integrations that relied on internal, undocumented APIs or specific behaviors of the previous Cline IDE extension architecture, those integrations will no longer function as expected. The underlying architecture and communication protocols have changed.

Before (Conceptual - Old IDE Extension Integration):

// old-custom-ide-extension.ts (BEFORE - Relying on internal Cline extension APIs)
// This API might have been internal and is now removed or changed.
declare const ClineIDE: {
  getLegacyWorkspaceContext(): any;
  registerOldCommand(commandId: string, handler: Function): void;
};

ClineIDE.registerOldCommand('my.custom.cline.command', () => {
  const context = ClineIDE.getLegacyWorkspaceContext();
  // ... perform actions using old Cline internal logic
});

After (Conceptual - New IDE Extension Integration): You will need to adapt your custom extensions to use the new, standardized SDK APIs provided by Cline SDK 1.0.0. This ensures compatibility and allows your integrations to benefit from the SDK’s advanced features.

// new-custom-ide-extension.ts (AFTER - Using the new Cline SDK)
import { ProjectContext, AgentRuntime, CodeChange } from '@cline/sdk';
import * as vscode from 'vscode'; // Or other IDE API

export function activate(context: vscode.ExtensionContext) {
  vscode.commands.registerCommand('my.custom.cline.newCommand', async () => {
    const currentWorkspace = vscode.workspace.workspaceFolders?.[0]?.uri.fsPath;
    if (!currentWorkspace) {
      vscode.window.showErrorMessage('No workspace open.');
      return;
    }

    // Initialize Cline SDK context
    const projectContext = new ProjectContext(currentWorkspace);
    const myAgent = new MyCustomAgent(); // Your agent built with @cline/sdk

    try {
      const changes: CodeChange[] = await myAgent.run(projectContext);
      // Apply changes using IDE's API, e.g., vscode.workspace.applyEdit
      vscode.window.showInformationMessage(`Agent completed with ${changes.length} changes.`);
    } catch (error: any) {
      vscode.window.showErrorMessage(`Agent failed: ${error.message}`);
    }
  });
}

// Your custom agent logic, built on the Cline SDK
class MyCustomAgent extends AgentRuntime {
  async run(context: ProjectContext): Promise<CodeChange[]> {
    // ... implement agent logic using SDK APIs
    return [];
  }
}

We strongly recommend reviewing the comprehensive new SDK documentation for the official API surface and best practices for integration.

Performance Improvements

This release brings a significant uplift in the core performance of Cline agents, specifically in their accuracy.

+15% Agent Accuracy on SWE-Bench

Through optimized rulesets (./clinerules), Cline agents have demonstrated an impressive +15% improvement in accuracy on SWE-Bench benchmarks.

Key Insight: This performance gain was achieved without requiring any LLM retraining or fundamental architectural changes. The focus was on refining the instructions and operational rules that guide the agents. This improvement directly benefits all agents powered by the new Cline SDK, leading to more reliable and effective code generation and modification.

This highlights the critical role of well-crafted agent rules in maximizing the potential of underlying LLMs. Developers are encouraged to explore and optimize their own ./clinerules configurations.

Security Vulnerabilities Addressed

No security vulnerabilities were addressed in this release.

Ecosystem Impact

The release of Cline SDK 1.0.0 is a pivotal moment for the entire Cline ecosystem, marking a strategic shift towards a more open and integrated future.

Standardized Agent Development

By open-sourcing the core agent runtime, Cline provides a standardized, extensible platform for developing AI agents. This moves Cline beyond a set of tools into a foundational technology for agentic AI. Developers can now build custom agents, integrate Cline’s capabilities into their own applications, and contribute to the core runtime.

Internal Adoption as a Blueprint

The fact that Cline’s own CLI, Kanban, and IDE extensions have been rebuilt or migrated to leverage the new SDK serves as a powerful testament to its capabilities and stability. This internal adoption provides a clear blueprint for how external developers can integrate and build upon the SDK, showcasing its versatility across different interface layers.

This release sets the stage for a thriving community around agentic AI, where developers can collaborate on improving the core runtime and building innovative applications on top of it.

How to Upgrade & Migration Guide

Given the “high” upgrade urgency and the foundational nature of Cline SDK 1.0.0, all users are strongly encouraged to upgrade.

Exact Upgrade Command

To install the latest Cline SDK and the new Cline CLI, run one of the following commands in your project directory:

# Using npm
npm install @cline/sdk@latest @cline/cli@latest

# Using yarn
yarn add @cline/sdk@latest @cline/cli@latest

Migration Guide for Existing Users

Since Cline SDK 1.0.0 represents a fundamental re-architecture and the removal of the old cli/ source tree, upgrading from previous internal Cline components involves a migration process rather than a simple update. Existing users are essentially transitioning to a new, SDK-centric approach.

  1. Remove Old Dependencies:

    • Thoroughly identify and remove any direct references, workspaces entries, or scripts that directly invoke the old cli/ source tree or rely on previous internal Cline APIs.
    • Review your package.json, build scripts, and any custom tools or IDE extensions for deprecated API calls or file paths.
    • Delete the old cli/ directory if it was part of your project’s workspace.
  2. Install New SDK and CLI:

    • Execute the upgrade command provided above to install the official @cline/sdk and @cline/cli packages.
  3. Update Integrations and Code:

    • Agent Scripts: Adapt your existing agent scripts to utilize the new, standardized APIs provided by the @cline/sdk.
    • Custom Tools: Rewrite any custom tools or automations that previously interacted with the old Cline CLI or internal components to use the new @cline/sdk or the new @cline/cli commands.
    • IDE Extensions: If you maintain custom IDE extensions, they must be updated to integrate with the new SDK’s API surface. Refer to the SDK documentation for detailed guidance.

While a comprehensive, dedicated migration guide is under development for future releases, this announcement blog post serves as the primary source of information for this foundational release. We recommend thoroughly reviewing the Introducing Cline SDK: the upgraded agent runtime for detailed insights into the new architecture and capabilities.

This upgrade is crucial for accessing the latest features, performance improvements, and aligning with the future development path of Cline.