> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/cloud-cost-management/integrations/sdk-integrations/open-source-sdks/claude-code.md).

# Claude Code

Use this integration for teams using Claude Code to generate or debug AI applications. Claude Code has OpenTelemetry export built in, so you do not add any instrumentation code. You enable telemetry and point the exporter at Harness.

Because the telemetry is native, both quickstart paths lead here to the same setup:

* **Route existing traces:** If you already run Claude Code with OpenTelemetry, you add one flag and set the Harness endpoint. No other changes.
* **Instrument your application:** If Claude Code is not emitting telemetry yet, the steps below turn it on. There is no separate SDK to install, because the exporter ships with Claude Code.

Before you start, generate an ingestion token and connect a provider. Go to the [AI Cost Management Quickstart](/cloud-cost-management/new-to-cacm/ai-cost-management/quickstart.md) for those steps. Replace `<YOUR_TOKEN>` below with that token and adjust the endpoint for your Harness cluster.

{% hint style="info" %}
**GENAI SEMANTIC CONVENTIONS REQUIRED**

Cost is calculated from OpenTelemetry traces with GenAI semantic conventions. Go to the [GenAI Span Attribute Reference](/cloud-cost-management/references/ai-cost-management/genai-span-attribute-reference.md) to review the attributes CACM reads.
{% endhint %}

***

### Configure Claude Code <a href="#configure-claude-code" id="configure-claude-code"></a>

[Claude Code](https://code.claude.com/docs/en/monitoring-usage) emits OpenTelemetry telemetry when you enable it. On top of the standard OpenTelemetry exporter variables, Claude Code additionally requires `CLAUDE_CODE_ENABLE_TELEMETRY=1` to turn telemetry on.

Set these environment variables in your shell profile, CI environment, or `~/.claude/settings.json`:

```bash
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_TRACES_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_ENDPOINT=https://app.harness.io/udp-ingest/otel
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <YOUR_TOKEN>"
```

| Variable                       | Purpose                                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| `CLAUDE_CODE_ENABLE_TELEMETRY` | The Claude Code flag that turns telemetry on. Without it, no traces are emitted.                                             |
| `OTEL_TRACES_EXPORTER`         | Selects the OTLP exporter for traces.                                                                                        |
| `OTEL_EXPORTER_OTLP_PROTOCOL`  | Selects HTTP/protobuf OTLP transport (Harness expects this format).                                                          |
| `OTEL_EXPORTER_OTLP_ENDPOINT`  | Harness OTLP trace ingestion endpoint. Replace `app.harness.io` with your cluster if different (example: `app3.harness.io`). |
| `OTEL_EXPORTER_OTLP_HEADERS`   | Bearer token for authentication. Use the literal token value or reference it from a secret or environment variable.          |

After setting the variables, restart Claude Code so they take effect.

{% hint style="info" %}
**TRACE EXPORT IS A BETA CAPABILITY**

Trace export from Claude Code is a beta capability. Go to the [Claude Code monitoring docs](https://code.claude.com/docs/en/monitoring-usage) to review the latest configuration and the list of emitted metrics, events, and traces.
{% endhint %}

***

### Verify Traces in Cost Explorer <a href="#verify-traces-in-cost-explorer" id="verify-traces-in-cost-explorer"></a>

1. Run Claude Code so telemetry flows. Traces usually appear within a few minutes; allow up to about 20 minutes.
2. Go to **Cloud & AI Cost Management** > **Cost Explorer**.
3. Select the **AI Traces** view or group by **Service Name**, and find your service.
4. Select a service row to open the **Service Traces** drawer and inspect the span waterfall.

***

### Next Steps <a href="#next-steps" id="next-steps"></a>

* Go to [Supported Providers and Frameworks](/cloud-cost-management/references/ai-cost-management/supported-providers-and-frameworks.md) to check native GenAI export support.
* Go to the [GenAI Span Attribute Reference](/cloud-cost-management/references/ai-cost-management/genai-span-attribute-reference.md) to review the exact attributes CACM reads.
* Go to [AI Cost Troubleshooting](/cloud-cost-management/resources/ai-cost-troubleshooting.md) if traces do not appear or show no cost.