Saoud Rizwan
c227e1ae36
* fix(vscode): restore legacy workflow invocation and management UI - Expand /workflow slash commands typed with the legacy .md filename spelling (what the autocomplete menu inserts) and mid-message, and honor the user's workflow enable/disable toggles, instead of only expanding a leading extension-less /name via the SDK resolver. - Restore the Workflows tab in the rules modal (view, toggle, create, edit, delete; enterprise section) that was dropped in the SDK-backed extension while all its gRPC handlers remained wired. * chore: add changeset for workflow fixes * fix(vscode): refresh workflow toggles on webview launch The slash command menu is driven by workflowToggles state, but nothing refreshed it at startup in the SDK-backed extension (only opening the rules modal or creating a rule file did), so workflows never appeared in the chat autocomplete until the user opened the modal. Legacy refreshed toggles on task init. * feat(vscode): move Workflows tab last and add deprecation warning Workflows tab now appears after Rules/Hooks/Skills, and its view leads with a warning banner: workflows are being deprecated in favor of skills, with a docs link. * chore: update changeset for workflow deprecation notice * fix(vscode): address review findings on workflow expansion - Honor remoteWorkflowToggles (and locked alwaysEnabled remote workflows) when building the disabled set, so disabled enterprise workflows no longer expand. - Treat a workflow as disabled only when no scope has it enabled, so a disabled workspace file no longer shadows a same-named enabled global one (legacy expanded the enabled scope). - Strip all workflow extensions the SDK discovers (.md/.markdown/.txt) when matching typed commands, not just .md. - Re-read toggle state after the async directory scan in refreshWorkflowToggles so a toggle flipped mid-scan is not overwritten by the stale snapshot. * fix(vscode): map workflow toggles to records so frontmatter names are governed Compute the disabled set from the discovered workflow records (listRecords) instead of toggle-path basenames alone: a file's toggle is matched by its basename and disables the record's actual command name, so a frontmatter 'name' that differs from the filename is still governed by the Workflows toggle. Remote-config-materialized records are governed by the name-keyed remote toggles (locked alwaysEnabled remain on). * fix(vscode): harden workflow toggle-name mapping for expansion - A command name shared by several records now counts as enabled when any record is enabled, so a disabled local workflow can no longer suppress an enabled or locked (alwaysEnabled) enterprise workflow. - Remote toggles/locks are matched via a sanitizeSegment-compatible key, so config names that get rewritten during materialization (e.g. 'Org Standards' -> org-standards.md) still govern expansion. - Typed filenames (e.g. /my-workflow.md from autocomplete) now resolve to workflows whose frontmatter renames the command, via the record's file basename. * fix(vscode): govern each workflow command by its own record's toggle Key the disabled set by exact command name and decide each record independently instead of OR-aggregating by canonical name: distinct commands whose names only differ by case or extension (e.g. a local 'Release' and a remote 'release') no longer influence each other, so an enabled local workflow cannot keep a disabled enterprise workflow expandable, and a disabled one cannot suppress a locked enterprise workflow. * fix(vscode): exact remote-name sanitization and keep mid-scan toggle additions - Port @cline/shared's sanitizeSegment verbatim (incl. the 80-char cap) for remote workflow name comparison, so long enterprise workflow names cannot bypass a disabled toggle after filename truncation. - The post-scan toggle merge now also keeps entries added while the scan was running (e.g. a workflow created via the modal), instead of pruning them with the deleted files. * fix(vscode): handle mid-scan deletions and sanitized remote-name collisions - The post-scan toggle merge now also drops entries that were removed from state while the scan ran, so a workflow deleted mid-refresh is not restored by the stale scan result. - Remote toggle names that sanitize to the same materialized name merge as enabled-if-any-enabled instead of last-write-wins. * fix(vscode): serialize workflow toggle refreshes Queue refreshWorkflowToggles runs on a promise chain so overlapping refreshes (webview launch, modal open, file create/delete) cannot interleave scans and writes. Combined with the post-scan merge for direct toggle flips, this closes the remaining stale-refresh races. * fix(vscode): key remote workflow toggles off the materialized filename The materializer names remote workflow files from the config name, so derive the remote toggle key from the file basename instead of the parsed command name; a frontmatter alias can no longer bypass a disabled remote toggle.
Cline
The open source coding agent in your IDE and terminal.
CLIRun Cline in your terminal. Interactive chat or fully headless for CI/CD and scripting. |
KanbanRun many agents in parallel from a web-based task board. Each card gets its own worktree, auto-commit, and dependency chains. |
VS Code ExtensionAI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval. |
JetBrains PluginThe same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family. |
SDKBuild your own AI agents and integrations powered by the same engine that runs the CLI, Kanban, VS Code extension, and JetBrains plugin. Custom tools, multi-agent teams, connectors, scheduled automations, and more. |
Index
| Product | Description | Location | CHANGELOG |
|---|---|---|---|
| SDK | Node.js programmatic agent API and extension exports. | sdk/ |
CHANGELOG.md |
| CLI | Terminal UI, headless mode, shell commands, and CLI-specific flows. | apps/cli/ |
CHANGELOG.md |
| VS Code Extension | The Marketplace extension and extension host integration. | / (WIP migrating) |
CHANGELOG.md |
| JetBrains Plugin | JetBrains-hosted client that talks to the shared agent core. | Currently we are not open-sourcing JetBrains plugins | - |
| Kanban | Web-based multi-agent task board. | cline/kanban |
CHANGELOG.md |
| Docs site | Public documentation pages. | docs/ |
- |
Edits Code Across Your Project
Cline reads your project structure, understands the relationships between files, and makes coordinated changes across your codebase. It monitors linter and compiler errors as it works, fixing issues like missing imports, type mismatches, and syntax errors before you even see them. In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert. All changes are tracked with checkpoints, so you can easily undo the agent's work.
Runs Bash Commands
Cline executes commands directly in your terminal and watches the output in real time. Install packages, run build scripts, execute tests, deploy applications, manage databases. For long-running processes like dev servers, Cline continues working in the background and reacts to new output as it appears, catching compile errors, test failures, and server crashes as they happen.
Plan and Act
Toggle between Plan mode and Act mode. In Plan mode, Cline explores your codebase, asks clarifying questions, and lays out a strategy. Once you're aligned, switch to Act mode and Cline executes the plan. Every file edit and terminal command requires your approval, so you stay in control of what actually changes. Or toggle auto-approve and let Cline run autonomously.
Rules and Skills
Define project-specific rules in .clinerules files that guide how Cline works in your codebase: coding standards, architecture conventions, deployment procedures, testing requirements. Rules are picked up automatically by the CLI, VS Code extension, and JetBrains plugin. Use skills to let the model load specific rules when needed.
Works With Every Model
Cline is not locked to a single AI provider. Use whichever model fits your workflow:
| Provider | Models |
|---|---|
| Anthropic | Claude Opus, Sonnet, Haiku |
| OpenAI | GPT series models |
| Gemini series models | |
| OpenRouter | 200+ models from any provider |
| Vercel AI Gateway | Route to many providers through one gateway |
| AWS Bedrock | Claude, Llama, and more |
| Azure / GCP Vertex | All hosted models |
| Cerebras / Groq | Fast inference models |
| Ollama / LM Studio | Run local models on your machine |
| Any OpenAI-compatible API | Self-hosted or third-party endpoints |
Extend With Plugins or MCP Servers
Extend Cline's capabilities with plugins. Using the SDK, register tools and lifecycle hooks programmatically through the plugin system for logging, auditing, policy enforcement, or adding domain-specific capabilities. Simple plugin example below.
import { Agent, createTool } from "@cline/sdk"
const deployTool = createTool({
name: "deploy",
description: "Deploy the current branch to staging.",
inputSchema: { type: "object", properties: { env: { type: "string" } }, required: ["env"] },
execute: async (input) => {
// your deployment logic
},
})
const agent = new Agent({ tools: [deployTool], /* ... */ })
...or use MCP servers to connect to databases, query APIs, manage cloud infrastructure, and interact with external systems. Use community-built servers or ask Cline to create custom tools on the fly. In the CLI, manage servers with cline mcp.
Multi-Agent Teams
Coordinate multiple agents working together on complex tasks. A coordinator agent breaks the work into subtasks and delegates to specialist agents, each with their own tools and context. Team state persists across sessions so you can pick up where you left off.
cline --team-name auth-sprint "Plan and implement user authentication with tests"
Scheduled Agents
Run agents on cron schedules for recurring automations. Daily PR summaries, weekly dependency checks, codebase health reports. Schedules persist across restarts and run independently of any terminal session.
cline schedule create "PR summary" \
--cron "0 9 * * MON-FRI" \
--prompt "List all open PRs and their review status" \
--workspace /path/to/repo
Connect to Slack, Telegram, Discord, and More
Chat with your agent from any messaging platform: Telegram, Slack, Discord, Google Chat, WhatsApp, and Linear. Each conversation thread maps to an agent session with full context. Set up access control to restrict who can interact with your agent.
# Connect to Telegram
cline connect telegram -k $BOT_TOKEN
# Connect to Slack through webhook
cline connect slack --bot-token $SLACK_TOKEN --signing-secret $SECRET --base-url $URL
# Connect to Slack using socket mode
cline connect slack --bot-token $SLACK_TOKEN --app-token $SLACK_APP_TOKEN
Headless CLI for CI/CD
Run Cline with zero interaction for scripting and automation. Pipe input, get JSON output, chain commands, integrate into CI/CD pipelines.
cline "Run tests and fix any failures"
git diff origin/main | cline "Review these changes for issues"
cline --json "List all TODO comments" | jq -r 'select(.type == "agent_event" and .event.text) | .event.text'
Contributing
Start with the Contributing Guide. Join our Discord and head to the #contributors channel to connect with other contributors. Check our careers page for full-time roles.