Repo Pulse
Cline hits 60K stars with Claude Opus 4.7 support
Cline, an IDE-embedded autonomous coding agent with 60,475 stars, shipped Claude Opus 4.7 support and enterprise remote skills features in v3.79.0. The project closed 300 issues in 30 days while managing SDK stability and multi-provider compatibility issues.
Cline is an autonomous coding agent that runs directly in your IDE, capable of creating and editing files, executing commands, using a browser, and performing other actions with explicit user permission at each step. The project has reached 60,475 stars on GitHub and is actively shipping features at a weekly cadence, with v3.79.0 released on April 16 and v3.78.0 on April 10.
By the numbers
| Metric | Value |
|---|---|
| Current stars | 60,475 |
| 30-day commits | 64 |
| 30-day contributors | 16 |
| PRs merged (30d) | 55 |
| Issues opened (30d) | 151 |
| Issues closed (30d) | 300 |
| Recent releases (90d) | 10 |
| Days since latest release | 1 |
The project maintains a high issue-closure rate, closing 300 issues against 151 opened in the past month. Releases ship weekly or bi-weekly, with the most recent tag v3.79.0 published April 16, 2026. The contributor base expanded to 16 active developers in the past 30 days, suggesting sustained organizational investment.
What’s shipping
Recent merged PRs and commits reveal three dominant themes: model provider expansion, enterprise infrastructure, and stability hardening.
Model provider work dominates the latest cycle. PR #10286 prepared support for Anthropic’s Claude Opus 4.7, with documentation updates following in PR #10295. This reflects Cline’s tight integration with Anthropic’s model releases. The agent now tracks multiple LLM providers, and recent issues indicate users are experimenting with OpenAI-compatible endpoints (NVIDIA SDK) and Google Gemini 3 flash preview, though with mixed results on pricing accuracy and token counting.
Enterprise and remote features represent a second major thrust. PR #10283 wired up remote globalSkills with enterprise UI and architectural fixes, tagged as ENG-1774. This suggests Cline is building out multi-user or distributed agent capabilities for enterprise deployments. Supporting this, PR #10056 (merged April 15) introduced user-level remote-config discovery with inline value reuse, and documentation for Kanban remote access was added in PR #10274. These changes indicate the project is moving toward centralized configuration and skill management for larger deployments.
Stability and dependency management form a steady baseline. PR #10271 updated axios to 1.15.0 across all packages, a routine but necessary hygiene task. PR #10291 fixed flaky Windows CI test paths, addressing platform-specific brittleness. PR #10266 fixed cache reflection for Cline and Vercel handlers, suggesting integration with Vercel’s ecosystem. A recent commit (April 14) unblocked stuck command_output asks when terminal commands end, a subtle but important fix for agent responsiveness.
Documentation is receiving continuous attention. PRs #10195 and #10164 added prompt storage schema references, OpenTelemetry events documentation, and corrected enterprise license links. This level of documentation work suggests the project is maturing its observability and configuration story.
Across 55 merged PRs in 30 days, the ratio strongly favors features and architectural work over pure bugfixes, though the latter remain present. The team is balancing new capability (Claude Opus 4.7, remote skills) with platform stability (Windows CI, cache fixes, SDK shutdown behavior).
Open questions
Recent issues reveal friction points and unresolved design questions.
SDK and CLI stability surfaces in issue #10325, where agent.shutdown() may block indefinitely in CLI usage. This is a blocking issue for non-IDE deployments and suggests the SDK’s lifecycle management needs refinement for server or CLI contexts.
Multi-provider compatibility is strained. Issue #10306 reports that OpenAI-compatible providers using the NVIDIA SDK show inflated context token counts, unparsed tool calls, and rendering bugs with thinking tags. This indicates the abstraction layer over multiple LLM providers is leaky; token counting and tool-use serialization are not yet provider-agnostic. Issue #10314 flags incorrect pricing for Gemini 3 flash preview, implying pricing metadata is hardcoded or out of sync.
Platform integration gaps appear in issue #10312, where Cline fails to load on VS Codium (the open-source VS Code variant). This suggests the extension may depend on closed-source VS Code APIs or marketplace integration that Codium does not provide.
Vendor restrictions emerge in issue #10307, where a provider (Kimi) restricts API access to specific coding agents, blocking Cline users. This is outside Cline’s control but reflects the fragmentation of the coding agent ecosystem.
Data handling edge cases are being discovered. Issue #10324 reports that exporting a history item from a different WSL distro removes it from history without saving the export, indicating incomplete transaction semantics in multi-environment scenarios.
Performance concerns are starting to surface. Issue #10303 reports high CPU load from the extension, a symptom that could point to polling, inefficient watchers, or background indexing.
The issue backlog suggests the project is hitting the scaling challenges typical of mature IDE extensions: provider abstraction brittleness, platform-specific quirks, and performance tuning. The team closed 300 issues in 30 days, so triage velocity is strong, but the open set indicates users are pushing the agent into edge cases (remote WSL, non-standard editors, alternative LLM providers) that the core design may not have fully anticipated.
Takeaways
Cline is tightening its Anthropic integration while building enterprise multi-user infrastructure. The rapid adoption of Claude Opus 4.7 support and the introduction of remote globalSkills and user-level config discovery signal that Cline is positioning itself as an enterprise-grade agent platform, not just a VS Code extension. Developers evaluating Cline for team or production use should expect improved centralized configuration and skill management in coming releases, but should also test multi-provider scenarios (OpenAI, Gemini) carefully, as the abstraction layer is still leaky.
Release cadence and issue closure rates are strong, but multi-provider support is fragile. With 55 PRs merged and 300 issues closed in 30 days, the project maintains high velocity. However, issues #10306 and #10314 reveal that supporting multiple LLM providers introduces subtle bugs in token counting, tool calling, and pricing that are hard to catch in CI. Teams using non-Anthropic models should monitor the issue tracker closely and test thoroughly before relying on Cline in production.
The SDK and CLI story needs attention. Issue #10325 (agent.shutdown() blocking indefinitely) and the existence of a Cline SDK suggest the project is expanding beyond the IDE extension into programmatic use. This is a positive direction, but the lifecycle and error handling of the SDK appear incomplete. Organizations building on Cline’s SDK should expect rough edges and engage with the issue tracker.
Platform fragmentation is starting to constrain adoption. VS Codium incompatibility, WSL edge cases, and vendor API restrictions (Kimi) indicate that Cline’s reach is limited by ecosystem factors outside its control. Developers in non-standard environments should validate compatibility early.
Further reading
- The official Cline repository on GitHub, containing source code, issue tracker, and release notes for all versions.
- Anthropic’s Claude documentation, which covers the Opus 4.7 model and API integration details that Cline now supports.
- The Cline SDK documentation for programmatic agent usage and lifecycle management, relevant for non-IDE deployments.
- OpenTelemetry events reference in Cline’s docs, added in PR #10195, for observability and debugging of agent behavior.
- The v3.79.0 release notes, published April 16, detailing new features and known issues in the latest stable version.
Frequently asked
What is Cline and how does it differ from other coding agents?
Cline is an autonomous coding agent embedded directly in your IDE (primarily VS Code) that can create and edit files, run commands, use a browser, and perform other actions with explicit user permission at each step. It integrates tightly with Anthropic's Claude models and is designed for interactive use within the development environment, unlike server-side agents.
Does Cline support models other than Claude?
Yes, Cline supports multiple LLM providers including OpenAI, Google Gemini, and OpenAI-compatible endpoints. However, recent issues indicate that multi-provider support has rough edges: token counting may inflate, tool calls may not parse correctly, and pricing metadata can be inaccurate. Test thoroughly if using non-Anthropic models in production.
Is Cline suitable for enterprise or team use?
Cline is moving toward enterprise use with recent additions of remote globalSkills, user-level remote configuration discovery, and Kanban remote access. However, the project is still stabilizing these features. Teams should monitor the issue tracker and test thoroughly, particularly around multi-user scenarios and non-standard environments like WSL.
What are the current stability concerns with Cline?
Recent issues highlight SDK shutdown blocking in CLI contexts, high CPU load in the extension, platform incompatibility with VS Codium, and multi-provider bugs. Additionally, exporting history across WSL distros has data loss issues. These suggest the project is hitting scaling challenges typical of mature IDE extensions.
How often does Cline release updates?
Cline releases weekly or bi-weekly. In the past 90 days, 10 versions were released (v3.70.0 through v3.79.0), with v3.79.0 shipping on April 16, 2026. The project merged 55 PRs and closed 300 issues in the past 30 days, indicating sustained development velocity.