docs/enterprise-solutions/monitoring/telemetry.mdx
Cline includes telemetry to help understand usage patterns and improve the product. Users can control whether to share this data.
Telemetry captures anonymous usage events such as:
Individual users can control telemetry through Cline settings:
Changes take effect immediately.
When telemetry is enabled, Cline captures:
<AccordionGroup> <Accordion title="Feature Usage" icon="cursor-click"> - Tools executed (e.g., read_file, execute_command) - Slash commands used - Workflows triggered - Settings changed </Accordion> <Accordion title="Task Metrics" icon="tasks"> - Task started/completed events - Mode switches (Plan/Act) - Checkpoint usage - Task duration </Accordion> <Accordion title="Error Events" icon="triangle-exclamation"> - API failures - Tool execution errors - System errors - Error types and frequencies </Accordion> </AccordionGroup>Cline Telemetry never includes:
Administrators can set default telemetry state through remote configuration:
{
"telemetryEnabled": true
}
For organizations with additional compliance or monitoring requirements, Cline provides:
Automatically backup conversation history to AWS S3 or Cloudflare R2 for:
See Prompt Storage for configuration details.
Export detailed metrics and logs to your own observability platforms like Datadog, New Relic, or Grafana Cloud.
See OpenTelemetry for setup instructions.
Cline's telemetry is designed with privacy in mind:
<CardGroup cols={2}> <Card title="Anonymous" icon="user-secret"> No personal information is collected </Card> <Card title="Optional" icon="toggle-on"> Users can disable at any time </Card> <Card title="Local First" icon="laptop"> Code never leaves your machine </Card> <Card title="Transparent" icon="eye"> Open source - see exactly what's collected </Card> </CardGroup>Anonymous usage data helps: