[KongchangAI]
ProductCline SDK Core

@cline/core

The open-source core SDK package of the Cline project, providing the underlying agent loop and tool-calling protocol capabilities of an AI coding assistant, reusable by the CLI, other IDE plugins or third-party integrations; it is at an initial 0.0.x development stage.

Core Facts

Timeline (last 90 days)

Oct 13

Extracting the core logic from the editor extension into an independent SDK can bring reusability, version decoupling and test-friendliness.

Unverified50%
Oct 13

@cline/core v0.0.93 provides a comparison entry point for commit 1a5c3f8.

Unverified50%
Oct 13

@cline/core is in the 0.0.x stage and has not yet entered a period of stable API commitment, so its interfaces may still be adjusted rapidly.

Unverified50%
Oct 13

The more prudent way to use @cline/core is to hard-code an exact version (such as 0.0.93) in package.json rather than using a range notation like ^0.0.93.

Unverified50%
Oct 13

For ordinary users, SDK version updates in most cases take effect together with subsequent editor extension versions, requiring no manual intervention.

Unverified50%
Oct 13

The v0.0.93 release of @cline/core itself contains no public human-readable change description.

Unverified50%
Oct 13

The Release of @cline/core v0.0.93 comes with 2 build artifacts (Assets).

Unverified50%
Oct 8

@cline/core newly exports parseMcpHeaders for use by the CLI's mcp add wizard to preserve the values of --header.

Unverified50%
Oct 4

This release covers the sdk/core module, not the end-user extension itself.

Unverified50%
Oct 4

Extracting core capabilities from the plugin into a standalone SDK means third-party developers can build integrated applications based on the Core SDK without depending on a specific editor environment.

Unverified50%

2 more timeline events

All Facts (12)

Verified

Cline released version v0.0.90 of the sdk/shared package, corresponding to the npm package @cline/shared@0.0.90

80%
Unverified

Extracting the core logic from the editor extension into an independent SDK can bring reusability, version decoupling and test-friendliness.

50%
Unverified

@cline/core is in the 0.0.x stage and has not yet entered a period of stable API commitment, so its interfaces may still be adjusted rapidly.

50%
Unverified

The more prudent way to use @cline/core is to hard-code an exact version (such as 0.0.93) in package.json rather than using a range notation like ^0.0.93.

50%
Unverified

For ordinary users, SDK version updates in most cases take effect together with subsequent editor extension versions, requiring no manual intervention.

50%
Unverified

The v0.0.93 release of @cline/core itself contains no public human-readable change description.

50%
Unverified

The Release of @cline/core v0.0.93 comes with 2 build artifacts (Assets).

50%
Unverified

@cline/core v0.0.93 provides a comparison entry point for commit 1a5c3f8.

50%
Unverified

@cline/core newly exports parseMcpHeaders for use by the CLI's mcp add wizard to preserve the values of --header.

50%
Unverified

This release covers the sdk/core module, not the end-user extension itself.

50%
Unverified

Extracting core capabilities from the plugin into a standalone SDK means third-party developers can build integrated applications based on the Core SDK without depending on a specific editor environment.

50%
Unverified

For @cline/shared in the 0.0.x stage, it is recommended to use exact version numbers in package.json rather than ^ or ~ range specifiers to prevent automatic upgrades from triggering compatibility issues

50%

Source Articles