Cline

Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.

Comprehensive Cline SDK skill for building AI agents. Covers the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment. Use for any task involving @cline/sdk or its sub-packages.

Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.

Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.

Prepare and publish a release directly from main.

Create a hotfix release by cherry-picking specific commits from main onto the latest release tag.

Tools are how agents interact with the world. The Cline SDK supports both built-in tools (via ClineCore) and custom tools you define yourself.

ClineCore holds resources (file watchers, database connections, hub connections). Failing to call dispose() can leave orphan processes and file locks.

ClineCore is the full-featured runtime from @cline/core. It wraps the Agent loop with session persistence, built-in tools (bash, editor, file reading, search, web fetch), config discovery, plugin loading, and optional hub-backed multi-process support.

extensions passes plugin objects directly. pluginPaths points to directories with package.json containing a cline.plugins field. Set extensionContext.workspace so plugins receive ctx.workspaceInfo in their setup() call -- without it, ctx.workspaceInfo is undefined.

Auto-approve reads, require approval for writes:

The Cline SDK supports scheduled, one-off, and event-driven agent execution through the automation subsystem in @cline/core.

A Cline plugin is a TypeScript module that extends any agent built on the Cline SDK. The same plugin runs in the Cline CLI, VS Code and JetBrains extensions, and any custom app built on @cline/core.

The Cline SDK supports every major LLM provider out of the box via @cline/llms.

The Cline SDK supports two models for multi-agent work: sub-agents (parent-child) and teams (peer-to-peer).

If the agent keeps iterating without completing:

The Agent class (also exported as AgentRuntime) is the lightweight, stateless agent loop from @cline/agents. It handles the core iteration cycle: send messages to an LLM, execute tool calls, collect results, and repeat until the task is done.

Two config forms exist as a discriminated union:

A multi-turn conversational agent in the terminal with streaming output:

Guidelines for deploying Cline SDK agents in production environments.

The Cline SDK has three event layers. Which one you use depends on whether you're working with the standalone Agent class or ClineCore.

OpenTUI is built for Bun. Always use Bun commands:

The foundational library for building terminal user interfaces. Provides an imperative API with all primitives, giving you maximum control over rendering, state, and behavior.

Creates and initializes the CLI renderer.

Create renderables and compose with .add():

OpenTUI respects several environment variables for configuration and debugging.

OpenTUI uses the Yoga layout engine, providing CSS Flexbox-like capabilities for positioning and sizing components in the terminal.

OpenTUI provides a timeline-based animation system for smooth property transitions.

This is the most common mistake. Using process.exit() leaves the terminal in a broken state (cursor hidden, raw mode, alternate screen).

A SolidJS reconciler for building terminal user interfaces with fine-grained reactivity. Get optimal performance with Solid's signal-based approach.

Renders a Solid component tree into a CLI renderer.

Use Index when array items are primitives:

The CLI creates the my-app directory for you - it must not already exist.

How to test terminal user interfaces built with OpenTUI.

Reference for all OpenTUI components, organized by category. Components are available in all three frameworks (Core, React, Solid) with slight API differences.

Components for displaying text content in OpenTUI.

Components for user input in OpenTUI.

Components for grouping and organizing content in OpenTUI.

Components for displaying code with syntax highlighting and diffs in OpenTUI.

This is the most common mistake. Using process.exit() leaves the terminal in a broken state (cursor hidden, raw mode, alternate screen).

A React reconciler for building terminal user interfaces with familiar React patterns. Write TUIs using JSX, hooks, and component composition.

Options: - release?: boolean - Include key release events (default: false)

A prompt mirrored from cline/cline.

The CLI creates the my-app directory for you - it must not already exist.

How to handle keyboard input in OpenTUI applications.

- models.dev catalog data and AI SDK provider behavior are the default sources of truth for general model/provider support. - Do not build a broad Cline-maintained model capability or behavior registry. - GatewayModelCapability is semantic: what the model can do, not provider quirks, default behavior, or wire-format details. - Stable, reliable known-model facts belong in typed

This file applies to the SDK workspace rooted at this directory (sdk/). In this repo, "root" means the SDK workspace root unless explicitly stated otherwise. Ignore the legacy repository root for SDK development except for Git operations or repo-wide searches that are explicitly needed.

This directory contains the tool registration system for Cline tools. The system automatically collects and registers all tool variants with the ClineToolSet provider.

The system prompt architecture provides a modular, composable system for building AI assistant prompts. It supports multiple model variants, dynamic component composition, flexible tool configuration, and template-based prompt generation.

This directory contains integration tests for the system prompt generation with snapshot testing capabilities.

Contributing to System Prompts and Model Configuration