Skip to main content
Connect Cline to track AI-assisted code generation, task completion, and development productivity across your team.

​
What’s tracked

  • Code generation — AI-generated code from Cline sessions
  • Task metrics — Tasks completed with Cline assistance
  • Session activity — Usage frequency and duration
  • Tool selection — Which AI models and features are used

​
Prerequisites

  • Cline VS Code extension installed
  • Active Cline account (individual or enterprise)
  • For remote config: Cline enterprise organization

​
Setup

Cline can be connected to Weave using OpenTelemetry. Choose the method that works best for your team: Best for individual developers or small teams.
1

Create an API key

Go to Data → Cline → Connect and create a new API key
2

Copy the environment variables

Copy or download the environment variables shown in the configuration modal
3

Add to your shell profile

Add the environment variables to your shell profile. The generated configuration includes Cline-specific variables:For Zsh (macOS default):
For Bash:
Replace the ... values with those from the configuration modal. The exact values are pre-filled when you copy from Weave.
4

Restart VS Code

Restart VS Code to apply the environment variables
5

Verify connection

Use Cline and check that activity appears in Weave after a few minutes

​
Option 2: Remote configuration (For Cline Enterprise)

Best for organizations using Cline’s enterprise features. This method doesn’t require individual developers to set environment variables.
1

Create an API key in Weave

Go to Data → Cline → Connect and create a new API key
2

Open Cline's organization settings

Sign in to your Cline organization at app.cline.bot and go to Organization Settings → OpenTelemetry
3

Configure OpenTelemetry

Enter the following settings:
  • Enable OpenTelemetry: Enabled
  • Metrics exporter / Logs exporter: otlp
  • Protocol: Use the value shown in Weave’s configuration modal (either http/json or http/protobuf)
  • OTLP endpoint: Copy from Weave’s configuration modal
  • Headers: Add x-weave-token with your API key value
4

Save your settings

All organization members will automatically use this configuration when they’re logged into their Cline account
5

Verify connection

Have team members use Cline and verify activity appears in Weave
Remote Configuration is a Cline enterprise feature. Users must be logged into their Cline organization account for this to work.

​
Metrics enabled

Once connected, you can track:

​
Cost tracking

Cline’s OpenTelemetry stream reports activity but not dollar cost, so Weave does not pull per-token Cline spend. Cline also has no entry under Settings → Financial → Tool subscription costs, so Weave doesn’t currently report a Cline cost. If your team runs Cline against your own model API keys, the underlying model spend shows up under that provider’s integration (for example, OpenAI) rather than under Cline.

​
Sync frequency

Cline data syncs in real-time via OpenTelemetry when the extension is active.

​
Troubleshooting

If Cline data isn’t syncing with environment variables:
  1. Verify environment variables are set correctly (echo $CLINE_OTEL_EXPORTER_OTLP_ENDPOINT)
  2. Ensure you restarted VS Code after setting variables
  3. Check that Cline extension is up to date
  4. Try setting variables in a .env file in your workspace
  5. Verify the API key is valid in Weave settings
If enterprise remote config isn’t syncing:
  1. Verify users are logged into their Cline organization account
  2. Check that OpenTelemetry is enabled in organization settings
  3. Ensure the OTLP endpoint URL is correct
  4. Verify the x-weave-token header is set properly
  5. Check Cline organization logs for connection errors
If Cline activity isn’t tracked:
  1. Wait 5-10 minutes after first Cline usage
  2. Verify Cline extension is actively being used
  3. Check that OpenTelemetry is configured correctly
  4. Ensure network access to Weave’s OTLP endpoint
  5. Review browser console for connection errors
If generated code isn’t attributed to Cline:
  1. Ensure code changes are being committed to git
  2. Verify git repositories are connected to Weave
  3. Check that commit metadata includes Cline information
  4. Review Cline settings for telemetry options

​
Configuration comparison

​
Data privacy

Weave syncs usage metadata and prompt content from Cline:
  • Usage frequency
  • Code generation statistics
  • Model usage (which AI models are used)
  • User prompt text from AI-assisted commits (used for activity classification)
We never access:
  • Source code content or diffs
  • Cline’s responses
  • File paths or project structure
Last modified on October 17, 2026