claude-code-tracing

Arize Coding Harness Tracing

Trace AI coding sessions to Arize AX or Phoenix with OpenInference spans. Each harness integration emits spans for prompts, tool calls, model responses, and session lifecycle events.

Supported Harnesses

Harness Integration	Install command	Name
Claude Code CLI / Agent SDK	macOS / Linux · Windows	claude
Claude Code CLI / Agent SDK	Claude Plugin	claude-code-tracing
OpenAI Codex CLI	macOS / Linux · Windows	codex
Cursor IDE / CLI	macOS / Linux · Windows	cursor
GitHub Copilot (VS Code + CLI)	macOS / Linux · Windows	copilot
Gemini CLI	macOS / Linux · Windows	gemini
Kiro CLI	macOS / Linux · Windows	kiro
Opencode CLI	macOS / Linux · Windows	opencode
Oh My Pi (omp)	macOS / Linux · Windows	omp

Each install link opens the ready-to-paste command for your OS — copy it and run it in a terminal

Installing Claude Code tracing via the Claude marketplace? See Claude Code Tracing for the marketplace-specific flow — backend credentials must be set directly in ~/.claude/settings.json since the install wizard is skipped.

Setup walkthrough

The installer involves a brief interactive setup. The steps below run in order:

1. Backend selection

Choose where spans should be sent:

• 1) Phoenix — your own Phoenix instance.
• 2) Arize AX — the hosted Arize platform.

2. Credentials

Prompts depend on the backend:

• Phoenix:
  • endpoint (defaults to http://localhost:6006)
  • optional API key (leave blank for no auth)
• Arize AX:
  • Arize API key
  • Space ID (found in Arize settings tab along with api keys)
  • OTLP endpoint (defaults to otlp.arize.com:443 — only override for hosted/dedicated instances).

If you've already configured another harness against the same backend, the installer offers a copy-from menu so you can reuse those credentials instead of re-entering them.

3. Project name

The project (in Arize/Phoenix) that spans for this harness are grouped under. Defaults to the harness name (e.g. claude-code, codex etc).

4. User ID (optional)

A free-form identifier attached to every span as user.id. Useful when multiple teammates share the same backend. Leave blank to skip.

5. Content logging

Three Y/n opt-outs that apply to all harnesses:

• Log user prompts?
• Log what tools were asked to do (commands, file paths, URLs)?
• Log what tools returned (file contents, command output)?

You're only asked these the first time you install a harness — subsequent installs reuse the existing logging: block. You can edit them later in ~/.arize/harness/config.json.

Environment variables

Most settings live in .arize/harness/config.json, but a small set of env vars affect runtime behavior on every harness. The installers wire most of these for you; set them yourself when you want to override behavior for a single session or debug locally.