Report coding tool metrics to Kimchi

When developers use Kimchi's Serverless Endpoints through AI coding tools, you can configure those tools to report usage telemetry back to Kimchi. This gives you a unified view of serverless endpoint consumption: token usage, costs, and tool activity across all your AI-assisted coding tools in a single place.

Claude Code

Claude Code supports OpenTelemetry (OTel) natively. Administrators configure telemetry export through Claude Code's managed settings file, so individual developers don't need to set anything up themselves.

Before you start

Before you configure metrics reporting, ensure:

• You have a Kimchi API key — Generate one from the Kimchi console under API Keys.
• Claude Code is installed in your organization — see Claude Code installation for setup instructions.
• You have access to configure Claude Code's managed settings file — see Claude Code managed settings for file locations by platform.

Configure the managed settings file

Add the following env block to your Claude Code managed settings file:

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_LOGS_PROTOCOL": "http/json",
    "OTEL_EXPORTER_OTLP_LOGS_ENDPOINT": "https://api.kimchi.dev/aioptimizer/v1beta/logs:ingest",
    "OTEL_EXPORTER_OTLP_LOGS_HEADERS": "Authorization=Bearer $YOUR_KIMCHI_API_KEY",
    "OTEL_LOGS_EXPORT_INTERVAL": "5000"
  }
}

Replace $YOUR_KIMCHI_API_KEY with the API key you generated from the Kimchi console.

Verify telemetry is reaching Kimchi

After developers start using Claude Code with the managed settings applied:

1. Open Claude Code and run a few prompts to generate telemetry data.
2. Navigate to the Kimchi console and check for incoming usage data.

If data is not appearing, check the following:

• Confirm the managed settings file is in the correct location and contains valid JSON.
• Verify the Kimchi API key is valid and has not expired.
• Ensure the machine running Claude Code has network access to api.kimchi.dev.

What data does Claude Code export?

Claude Code's OpenTelemetry events include structured data for each interaction:

• API requests — each API call Claude Code makes, including model, token counts, and cost.
• Tool results — tool executions, including tool names and execution parameters.
• User prompts — records when a user submits a prompt (prompt content is not exported by default).

Each event includes a prompt.id attribute that ties all activity back to the prompt that triggered it. Telemetry is opt-in and requires explicit configuration. Raw file contents and code snippets are not included in events. For full details, see Claude Code monitoring.

OpenCode

For OpenCode, install the OpenCode OTel plugin and follow the setup steps in its README. The plugin exports the same kind of telemetry — API requests, tool calls, token counts, and costs — to your Kimchi tenant.

Refer to the README at github.com/castai/opencode-otel-plugin for installation, configuration, and verification steps. When the README references an AI Enabler endpoint or API key, substitute your Kimchi endpoint (https://api.kimchi.dev/aioptimizer/v1beta/logs:ingest) and Kimchi API key.