Cline v4.1.4 リリースCline Releases v4.1.4

Cline, the open-source AI coding agent that runs inside editors such as Visual Studio Code, has published version 4.1.4, a focused release that broadens model provider support and refines how users interact with the tool's command system and its plan-and-act workflow. The update matters to developers who rely on Cline for agentic coding because it hands more control over mode transitions back to the user while widening the range of backends available for running models.

The headline addition is recognition of Chutes as a provider. Chutes is an inference platform that exposes access to large language models, and its inclusion means Cline users can select it directly rather than relying on a manual workaround or a generic endpoint configuration. Provider breadth has become a defining characteristic of tools in this category, because it lets teams weigh cost, latency, model availability, and data-handling preferences without abandoning their editor or assistant. By formally recognizing Chutes, Cline appears to be continuing a pattern of accommodating a growing field of inference options alongside established names like Anthropic, OpenAI, and aggregators such as OpenRouter.

The release also reworks the slash command menu, which is how Cline users trigger predefined actions from within a chat or task. Two changes stand out. First, skills are now shown alongside workflows in the same menu, giving both types of reusable capability equal visibility rather than surfacing one and hiding the other. Second, commands that share a name are now disambiguated instead of letting one shadow the other. Previously, when two entries carried the same identifier, one could effectively mask the other, making it unclear which action would run. The new behavior is intended to make command selection more predictable, particularly for users who accumulate a mix of custom workflows and skills over time.

The most consequential behavioral change concerns plan mode. Cline separates work into a planning phase and an acting phase: plan mode is meant for reading, analyzing, and proposing an approach, while act mode is where the agent actually edits files and executes changes. In earlier versions, the model itself could initiate the switch from plan to act, meaning the assistant could decide on its own that it was ready to begin making changes. Version 4.1.4 removes that model-initiated switching. Moving out of plan mode is now driven by the user, so the transition from proposing to executing requires an explicit human action.

That adjustment reflects a broader tension in agentic tooling between autonomy and control. Letting a model advance itself from planning to acting can reduce friction, but it also risks the agent beginning to alter a codebase before the developer has reviewed or agreed to the plan. By making the switch user-driven, Cline makes the boundary between analysis and modification more deliberate, which is likely to appeal to developers working in sensitive repositories or who want a clear checkpoint before any file is touched. The change does not remove the two-mode structure; it changes who is permitted to cross between the modes.

For context, Cline sits within a fast-moving segment of AI-assisted development that includes editor-integrated agents and command-line tools such as Cursor, GitHub Copilot's agent capabilities, Windsurf, Continue, and Aider. Many of these tools have converged on similar concepts: separating planning from execution, supporting multiple model providers, and offering reusable commands, workflows, or skills that let teams codify repeatable tasks. Features like slash commands and workflows function as lightweight automation layers, while skills represent packaged capabilities the agent can invoke, and clearer handling of both helps users scale their configurations without collisions.

As a point release in the 4.1.x line, v4.1.4 is incremental rather than a major overhaul, and the changes are best read as refinements to reliability and user control rather than new headline functionality. Still, the combination of an additional provider, a cleaner command menu, and a stricter plan-to-act boundary signals continued attention to predictability and choice. Developers already using Cline can update through their extension marketplace or the project's release channel to pick up the changes.