Skip to main content
Cline sends usage and error telemetry so that we can see how it’s used and fix problems. Telemetry is on by default in the VS Code and JetBrains extensions, Cline Desktop and the CLI, whether you sign in to a Cline account or use your own API keys. You can turn it off at any time.

​
What telemetry includes

Telemetry records events such as:
  • Features used, such as tools, slash commands and skills
  • Tasks started and completed, and switches between Plan and Act
  • Errors, such as API failures and tool errors
  • Token counts, timings, and model and provider names
  • Your Cline version, operating system and editor
Each installation has a device identifier. When you’re signed in to a Cline account, events also identify your account and organization. OpenTelemetry Events lists each event.

​
Code and prompts

Cline’s telemetry doesn’t include your code, file contents or prompts, except for requests to the Cline and ClinePass providers. Those providers receive your prompts so that they can run the model, and telemetry for these requests can include the prompt and the model’s response. With any other provider, your prompts go to that provider, and Cline’s telemetry doesn’t record them. The privacy policy describes how Cline handles the data it receives.

​
Turning telemetry off

These products share one telemetry setting on each computer. Turning it off in one product turns it off in the others.
  1. In the Cline panel, click the settings (gear) icon.
  2. Select General.
  3. Clear Allow error and usage reporting.
The change takes effect immediately. In VS Code, Cline also stops sending usage events while the editor’s own telemetry is off. While the editor’s telemetry is on, Cline still sends a few required events, such as the one that records that you turned Cline telemetry off.
In Cline Desktop and the CLI, Cline stops recording prompts from the next request, but other events continue until Cline and its background hub restart. To apply the change everywhere, quit Cline Desktop and run cline hub stop, or restart your computer. Stopping the hub also stops sessions running in it. The hub starts again the next time you use Cline. With telemetry off, Cline still contacts its servers for other purposes: to sign you in, to check feature flags, and to run requests on the Cline and ClinePass providers.

​
Organization settings

Admins can turn telemetry on or off for all members with the Cline Telemetry setting in the organization’s remote configuration:
In the VS Code and JetBrains extensions, the setting shows a lock while the organization sets it, and members can’t turn telemetry on when the organization turns it off. Cline Desktop and the CLI ignore this setting; see which products support each control.

​
Enterprise Monitoring Features

For organizations with additional compliance or monitoring requirements, Cline provides:

​
Prompt Storage

Automatically backup conversation history to AWS S3 or Cloudflare R2 for:
  • Compliance and audit trails
  • Usage analysis and reporting
  • Disaster recovery
See Prompt Storage for configuration details.

​
OpenTelemetry Integration

Export detailed metrics and logs to your own observability platforms like Datadog, New Relic, or Grafana Cloud. See OpenTelemetry for setup instructions.

​
Why Telemetry Matters

Usage data helps us:
  • Identify bugs: Discover issues affecting users
  • Prioritize features: Focus on most-used capabilities
  • Improve performance: Find and fix slow operations
  • Enhance reliability: Track and reduce error rates

OpenTelemetry

Enterprise monitoring and observability

Event Details

See what data is collected