Harness Monitoring and Hooks with OpenTelemetry

Monitor AI coding harnesses through their hooks — export to any OTLP-compatible backend.

opentelemetry-hooks provides harness monitoring through harness hooks. A harness is the application or runtime that runs an AI coding agent: a CLI, an editor integration, or another agent runner. The hook turns supported lifecycle events into structured OpenTelemetry traces and logs for an OTLP-compatible backend. Integrations cover Claude Code, Codex, Cursor IDE / Cursor CLI, Gemini CLI, GitHub Copilot, OpenCode, Windsurf, and compatible runners such as Antigravity, using OpenTelemetry GenAI semantic conventions.

Captured harness events — prompt submissions, tool calls, shell commands, MCP interactions, file edits, subagent orchestration — become OpenTelemetry spans you can query, alert on, and visualize in Jaeger, Grafana, Datadog, Honeycomb, Coralogix, or any OTLP-compatible backend.

Note: Native telemetry from Claude Code, Codex, and Cursor describes harness internals, while otel-hook describes hook lifecycle and governance. The hook tags its own provenance and does not deduplicate native signals; downstream analysis can reconcile the two sources when both are enabled. See Cursor native export and hooks for correlation and accounting guidance.

How It Works

The hook is a lightweight Python command that your harness invokes for registered lifecycle events. The harness pipes a JSON payload to stdin, the hook processes it, emits OpenTelemetry spans and logs, and returns the harness-compatible success response on stdout so execution proceeds normally. Cursor permission hooks return {"permission": "allow"} so this telemetry observer does not block the operation. Most other events return {"continue": true}; Codex uses event-specific response contracts, so passive Codex hooks stay silent except for Stop, which still returns JSON. No sidecar, no daemon — just a command your harness calls. OpenCode uses a small plugin to forward its callbacks to the same command.

Harness event → stdin (JSON) → otel-hook → OpenTelemetry SDK → OTLP backend
                                 ↓
                          stdout: harness-specific response

Features

• Multi-harness support: One hook command, multiple harness integrations. The CLI can register Codex, Cursor, Claude Code, Gemini CLI, GitHub Copilot, OpenCode, and Windsurf. Managed setup commands stamp an explicit source flag such as otel-hook --cursor, otel-hook --codex, or otel-hook --claude; process-tree and payload inference remain compatibility fallbacks for legacy or unmanaged hooks.

• Session-level Traces: Groups all events within a session into a single trace with a 3-tier hierarchy:

gen_ai.client.session (root)
├── gen_ai.client.generation (gen-1)
│   ├── gen_ai.client.hook.UserPromptSubmit
│   ├── gen_ai.client.hook.PreToolUse
│   ├── gen_ai.client.hook.PostToolUse
│   └── gen_ai.client.hook.Stop
├── gen_ai.client.generation (gen-2)
│   ├── gen_ai.client.hook.UserPromptSubmit
│   ├── gen_ai.client.hook.PreToolUse
│   ├── gen_ai.client.hook.PostToolUse
│   └── gen_ai.client.hook.Stop

• GenAI Semantic Conventions: Emits OpenTelemetry GenAI attributes aligned with v1.37+ (gen_ai.provider.name, gen_ai.operation.name, gen_ai.request.model, gen_ai.usage.*, etc.) while preserving legacy gen_ai.system for backward compatibility.

• Harness Lifecycle Monitoring: Captures supported hooks across the lifecycle — sessions, prompts, tool usage, shell commands, MCP calls, file operations, subagents, errors, and more.

• Structured OTel Logs: Emits trace-correlated log records for MCP calls, shell executions, and tool usage — with full I/O payloads, server output, and duration. Logs are exported via OTLP alongside spans.

• Repo-Aware Context: Enriches telemetry with repository metadata such as vcs.repository.name when a git root can be resolved, and normalizes stored file-memory facts to repo-relative paths.

• Zero Setup: Auto-provisions a Python virtual environment on first run. No manual install needed.

• Privacy Controls: Built-in masking of emails, tokens, and usernames. Text capture is opt-in.

• JSON Config File: All settings in otel_config.json — no environment variable exports needed.

Supported Harnesses

Harness	Setup Command	Scope	Config Written
Cursor IDE / CLI	otel-hook setup --agent cursor	Global by default; use --no-global for project scope	~/.cursor/hooks.json or .cursor/hooks.json
Claude Code	otel-hook setup --agent claude	Global by default; use --no-global for project scope	~/.claude/settings.json or .claude/settings.json
Codex	otel-hook setup --agent codex	Global by default; use --no-global for project scope	~/.codex/hooks.json and config.toml, or their project equivalents
Gemini CLI	otel-hook setup --agent gemini	Global by default; use --no-global for project scope	~/.gemini/settings.json or .gemini/settings.json
GitHub Copilot CLI / cloud agent	otel-hook setup --agent copilot	User-level CLI hooks by default; --no-global for repository/cloud hooks	~/.copilot/hooks/otel-hooks.json (or $COPILOT_HOME/hooks/) or .github/hooks/otel-hooks.json
OpenCode	otel-hook setup --agent opencode	Global by default; use --no-global for project scope	~/.config/opencode/plugins/otel-hook.ts or .opencode/plugins/otel-hook.ts
Windsurf	otel-hook setup --agent windsurf	Global by default; use --no-global for project scope	~/.codeium/windsurf/hooks.json or .windsurf/hooks.json
Antigravity / compatible runners	Manual hook command	Runner-defined	Runner workflow/config

Run otel-hook diagnose to see what is currently registered. Run otel-hook doctor for registration, privacy, exporter-health, and pending-delivery diagnostics. Use otel-hook uninstall --agent <agent> to remove this hook from a harness config.

Supported Events

Current first-party contracts and deliberate exclusions are recorded in Hook coverage.

Harness	Registered events / callbacks	Coverage
Claude Code	31	Permissions, notifications, failure stops, tasks/teams, instruction/config/workspace changes, model switches, elicitation, streamed message facts
Codex	12	Session end, compaction, subagents, interruption
Cursor	21	Compaction, Tab read/edit, responses/thoughts, workspace open
Gemini CLI	11	Tool selection, notification, pre-compression; corrected turn boundaries
Copilot	14	Turn end, tool failures, subagents, compaction, permissions, notifications, transformed prompts
Windsurf / Cascade	11	Native file, shell, MCP, prompt, response and worktree events
OpenCode plugin	11	Compaction, permission requests/replies; corrected session/message payloads
Antigravity / compatible runners	Manual	Existing compatibility adapter; no verified native installer

Gemini BeforeAgent / AfterAgent become UserPromptSubmit / Stop. Model callbacks remain separate observations and do not open or close turns. Windsurf uses trajectory_id for the session and execution_id for the generation. Copilot commands include --copilot --event <name> because native camelCase payloads omit the event name. Original event names remain available on spans.

Raw conversation content is opt-in. New message, notification, reasoning and task facts follow the existing length/hash contract. MessageDisplay records response chunks, not complete responses. Gemini nested model messages/chunks are omitted; model names and callback occurrence are observed without duplicating native token accounting.

Rerun the setup command for the relevant harness to register new events. Installing the updated package alone does not rewrite existing harness settings. Current documentation can describe features absent from older installed harness versions; these contracts are tested with fixtures, not a live session in every harness.

Compatibility and Migration

“Harness” is the product term used throughout this guide. Existing public identifiers remain supported: the otel-hook command, --agent option, IDE_OTEL_* settings, ide / ide_name payload fields, and default names such as ide-agent and ide-hooks. This terminology update does not rename configuration keys, telemetry attributes, or defaults. “IDE” still appears in editor product names and accepted identity aliases.

The expanded hooks replace some incorrect behavior: Windsurf now registers native events in hooks.json, Gemini uses agent callbacks for turn boundaries, and OpenCode errors no longer close the session. Existing Copilot users who want repository-scoped CLI setup should specify --no-global. See migration notes before updating registrations or queries based on the old behavior.

Installation

# Recommended: pipx keeps otel-hook on PATH in an isolated venv
pipx install opentelemetry-hooks

# Or with pip
pip install opentelemetry-hooks

To pin a specific version or install directly from a tag:

pipx install git+https://github.com/o11y-dev/opentelemetry-hooks.git@v0.15.0

Or install from a pre-built wheel from the Releases page:

pipx install opentelemetry_hooks-*.whl

Once installed, run otel-hook setup to wire your agents.

Quick Start

One-Command Setup (pip/pipx install)

After installing the package, configure your agents with the built-in CLI:

# Auto-detect all installed agents and configure globally
otel-hook setup

# Configure a specific agent
otel-hook setup --agent claude
otel-hook setup --agent cursor
otel-hook setup --agent copilot --no-global   # project-scoped (run from repo root)
otel-hook setup --agent gemini
otel-hook setup --agent codex
otel-hook setup --agent opencode
otel-hook setup --agent windsurf

# Project-scoped instead of global
otel-hook setup --agent cursor --no-global
otel-hook setup --agent codex --no-global
otel-hook setup --agent windsurf --no-global

# Check registration status
otel-hook diagnose

# Remove hooks
otel-hook uninstall --agent claude

Setup is idempotent — safe to re-run. Then configure your OTLP endpoint:

vim ~/.local/share/opentelemetry-hooks/otel_config.json

Python API (importable)

The setup functions are importable for programmatic use:

from otel_hook import setup_claude, setup_cursor, setup_gemini, setup_windsurf

setup_claude(global_=True)   # ~/.claude/settings.json
setup_cursor(global_=True)   # ~/.cursor/hooks.json
setup_gemini(global_=True)   # ~/.gemini/settings.json
setup_windsurf(global_=True) # ~/.codeium/windsurf/hooks.json

Source Checkout Setup

If you're working from a source checkout rather than a pip install, use the bundled setup.sh:

# Auto-detect installed/supported agents and configure them
bash setup.sh

# Configure one agent
bash setup.sh --cursor --global
bash setup.sh --claude --global
bash setup.sh --gemini --global
bash setup.sh --copilot       # repository-scoped
bash setup.sh --opencode --global

Then edit your endpoint config and restart the configured agent:

vim otel_config.json

Clone Into an Existing Project

If your project doesn't have the hook yet, copy the entire hook directory and run setup:

# Clone the hook repo and copy the essential files into your project
git clone https://github.com/o11y-dev/opentelemetry-hooks.git /tmp/otel-hook-source
mkdir -p .cursor/hooks/opentelemetry-hook
cp /tmp/otel-hook-source/otel_hook.py .cursor/hooks/opentelemetry-hook/
cp /tmp/otel-hook-source/setup.sh .cursor/hooks/opentelemetry-hook/
cp /tmp/otel-hook-source/otel_config.example.json .cursor/hooks/opentelemetry-hook/
cp /tmp/otel-hook-source/.gitignore .cursor/hooks/opentelemetry-hook/
cp -r /tmp/otel-hook-source/examples .cursor/hooks/opentelemetry-hook/

# Run setup — creates/merges hooks.json automatically
bash .cursor/hooks/opentelemetry-hook/setup.sh
rm -rf /tmp/otel-hook-source

Prerequisites

• Python 3.12+ (the setup script checks for this)
• An OTLP-compatible backend (Jaeger, Coralogix, Datadog, Grafana, Honeycomb, etc.)

Other Harnesses

Cursor CLI

Cursor CLI uses the same .cursor/hooks.json configuration and hook payload shape as Cursor IDE, so the Cursor IDE setup above in Quick Start also covers Cursor CLI. Its spans are recorded with the canonical gen_ai.client.name=cursor.

Windsurf

Windsurf uses native Cascade snake_case events in hooks.json. Project setup updates an existing active .devin/hooks.json when present, otherwise the backward-compatible .windsurf/hooks.json:

# Global Windsurf settings (~/.codeium/windsurf/hooks.json)
otel-hook setup --agent windsurf

# Project-scoped Windsurf settings (.windsurf/hooks.json)
otel-hook setup --agent windsurf --no-global

Windsurf spans are recorded with the canonical gen_ai.client.name=windsurf.

GitHub Copilot

# Repo-scoped hooks file (.github/hooks/otel-hooks.json)
bash setup.sh --copilot

setup.sh --copilot creates or merges .github/hooks/otel-hooks.json and points each event directly at otel-hook (or the local otel_hook.py fallback). The command supplies --copilot --event <name> so native payloads retain their source and event identity.

Copilot CLI also supports user hooks: run otel-hook setup --agent copilot or bash setup.sh --copilot --global. COPILOT_HOME overrides the default ~/.copilot directory. For the cloud agent, commit the repository hook file and ensure the hook runtime is available in its environment.

If you prefer a manual install, copy the bundled example instead:

mkdir -p .github/hooks
cp examples/copilot-hooks.example.json .github/hooks/otel-hooks.json

Then replace {{SCRIPT_PATH}} with the hook command. For a copied-source checkout the default is python3 .cursor/hooks/opentelemetry-hook/otel_hook.py; use otel-hook only when the package is installed via pipx or pip. See GitHub Copilot hooks docs.

Claude Code

mkdir -p .claude
cp examples/claude-hooks.example.json .claude/settings.json

Replace {{SCRIPT_PATH}} with the hook command, for example:

# source checkout / copied-source
python3 .cursor/hooks/opentelemetry-hook/otel_hook.py
# pip-installed package
otel-hook

The bundled Claude example and setup.sh --claude both invoke otel-hook directly without a harness identity override env var. Claude Code is auto-detected from the parent process tree first; hook metadata such as session_id, transcript_path, permission_mode, and notification_type is used as a fallback. The camelCase alias handling is mainly for compatible third-party hook runners and mixed payload formats.

Managed settings / enterprise rollout

If your org already deploys Claude Code managed settings (server-managed, MDM/registry, or file-based managed-settings.json), keep hook registration and hook exporter config as two separate concerns:

• Register otel-hook with the usual Claude hooks block (in project/user settings, or in managed settings if your org centrally manages hooks).
• Configure this hook's exporter in otel_config.json or this repo's own MDM/registry settings — not in Claude Code's env block.

Claude Code intentionally strips OTEL_* env vars from hook subprocesses, Bash, MCP servers, and language servers. otel-hook handles that safely by loading its own otel_config.json, then hook-side managed config, and only then filling any still-unset variables from the live process environment.

See examples/claude-managed-settings.example.json for a minimal managed-settings snippet for Claude Code's own telemetry.

Gemini CLI

# Global Gemini settings (~/.gemini/settings.json)
otel-hook setup --agent gemini

# Project-scoped Gemini settings (.gemini/settings.json)
otel-hook setup --agent gemini --no-global

For a source checkout, use:

bash setup.sh --gemini --global

Gemini CLI emits model, tool, and turn lifecycle events. BeforeAgent / AfterAgent mark the user turn; BeforeModel / AfterModel remain model observations, including streamed response chunks. PreCompress becomes PreCompact; BeforeToolSelection and Notification are passive observations.

Privacy note: Avoid putting sensitive prompts directly on the command line with gemini -p "...". Like most CLI arguments, the prompt can end up in shell history and may be visible in process lists while the command is running. Prefer interactive mode, stdin, or prompt files for sensitive input.

Antigravity

Antigravity workflow and hook formats can vary, so the simplest integration is to invoke the hook command directly from your workflow/rule and pin the harness name explicitly:

# source checkout / copied-source
env IDE_OTEL_IDE_NAME=antigravity python3 .cursor/hooks/opentelemetry-hook/otel_hook.py
# pip-installed package
env IDE_OTEL_IDE_NAME=antigravity otel-hook

An example Antigravity workflow is included in examples/antigravity-workflow.example.md:

mkdir -p .agent/workflows
cp .cursor/hooks/opentelemetry-hook/examples/antigravity-workflow.example.md .agent/workflows/opentelemetry-hook.md

Replace {{SCRIPT_PATH}} in the copied workflow with the hook command you want Antigravity to invoke. For a copied-source checkout use python3 .cursor/hooks/opentelemetry-hook/otel_hook.py; use otel-hook for a pip-installed package.

Codex

Codex hooks are configured in ~/.codex/hooks.json or <repo>/.codex/hooks.json and require the hooks feature flag in the matching config.toml.

Quick setup (recommended):

# Global — available in every Codex session
bash setup.sh --codex --global

# Project-level — only active for this project
bash setup.sh --codex

The setup command enables:

[features]
hooks = true

Manual install:

mkdir -p .codex
cp examples/codex-hooks.example.json .codex/hooks.json

Then replace {{SCRIPT_PATH}} with otel-hook or the absolute source checkout command.

Events captured: SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, and Stop. Codex does not currently emit a hook-level SessionEnd, so unfinished sessions are closed by this hook's stale-session cleanup when needed.

OpenCode

A native TypeScript plugin is included at plugin/opencode.ts. It hooks into OpenCode's session and tool lifecycle events and pipes JSON payloads to otel-hook on stdin — the same pattern used by rtk.

Quick setup (recommended):

# Global — available in every OpenCode session
bash setup.sh --opencode --global

# Project-level — only active for this project
bash setup.sh --opencode

Manual install:

# Global
mkdir -p ~/.config/opencode/plugins
cp plugin/opencode.ts ~/.config/opencode/plugins/otel-hook.ts

# Project-level
mkdir -p .opencode/plugins
cp plugin/opencode.ts .opencode/plugins/otel-hook.ts

Restart OpenCode after installing. The bundled plugin — including the copy installed by setup.sh --opencode — invokes otel-hook directly. The runtime prefers parent-process discovery, while the plugin's source_app: "OpenCode" payload field remains a compatibility fallback. OPENCODE_CONFIG_DIR is respected if set.

Events captured: SessionStart, SessionEnd, UserPromptSubmit, PreToolUse, PostToolUse, PostToolUseFailure (detected via metadata.exit), Stop, AfterFileEdit. Bash, read, write, MCP, and subagent (task) tool calls all flow through the universal tool.execute.before/after hooks and appear as PreToolUse/PostToolUse with the appropriate tool_name.

Other compatible runners

For any hook runner not listed above, invoke otel-hook (or python3 .../otel_hook.py) and forward compatible hook JSON on stdin. Pass a self-reported client field such as ide_name, client, or source_app with the value matching your tool, or set IDE_OTEL_IDE_NAME in the environment. When your runner uses camelCase payload keys such as sessionId, toolName, toolInput, or hookEventType, the hook normalizes them automatically before exporting spans.

GitHub Copilot — Recommended Repositories

To make this hook automatically available to the GitHub Copilot coding agent across your organization's repositories, add it as a recommended repository:

1. Go to your organization settings → Copilot → Coding agent → Recommended repositories
2. Add o11y-dev/opentelemetry-hooks to the list
3. The Copilot coding agent will now be able to reference this repo for hook setup and configuration

Configuration

Edit the hook config file. For pip/pipx installs this lives at ~/.local/share/opentelemetry-hooks/otel_config.json unless IDE_OTEL_HOOK_HOME is set. For a source checkout or copied-source install, edit the local otel_config.json next to otel_hook.py.

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4317",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

Then restart your harness.

Why the config file matters: otel-hook reads its own otel_config.json on every invocation, overlays this repo's MDM/registry policy, and only fills variables that are still unset from the live process environment. Explicit env vars still win, but the hook does not depend on parent-process OTEL_* inheritance. This is the safe path for Claude Code hooks, because Claude does not forward OTEL_* to hook subprocesses.

Configuration Reference

OTLP Exporter

Variable	Description	Default
OTEL_EXPORTER_OTLP_ENDPOINT	OTLP collector endpoint	http://localhost:4317
OTEL_EXPORTER_OTLP_PROTOCOL	grpc, http/protobuf, or http/json	grpc
OTEL_EXPORTER_OTLP_HEADERS	Auth headers (URL-encoded key=value pairs)	—
OTEL_SERVICE_NAME	Service name in traces	ide-agent

Note: OTEL_EXPORTER_OTLP_INSECURE is only used by the OTLP gRPC exporter (OTEL_EXPORTER_OTLP_PROTOCOL=grpc). It defaults to true (plaintext); set to false for TLS-secured gRPC endpoints. For http/protobuf and http/json exporters, TLS is determined by the endpoint scheme (https:// vs http://).

Hook Behavior

Variable	Description	Default
IDE_OTEL_BATCH_ON_STOP	Enable session-level batching (recommended)	false
IDE_OTEL_IDE_NAME	Force the detected harness name (codex, cursor, copilot, claude, gemini, antigravity, opencode, windsurf) for generic hook runners; common labels like OpenAI Codex, Codex CLI, GitHub Copilot, Claude Code, Cursor IDE / Cursor CLI, Gemini CLI, Anti Gravity, OpenCode, Windsurf IDE, Codeium Windsurf, and their ... CLI / ... IDE variants normalize automatically	auto-detect
IDE_OTEL_LOCAL_SPANS	Save hook spans locally as JSONL files for agent analysis (.state/local_spans/*.jsonl)	unset
IDE_OTEL_CAPTURE_CONVERSATION_CONTENT	Include prompt, response, stop-message, error, and delegation text in spans	false
IDE_OTEL_CAPTURE_TEXT	Legacy broad text-capture gate; also enables conversation content	false
IDE_OTEL_CAPTURE_USER_IDENTITY	Include opt-in user.id / user.email payload fields in spans and logs	false
IDE_OTEL_MASK_PROMPTS	Redact emails, tokens, usernames from text	false
IDE_OTEL_TEXT_MAX_CHARS	Max characters for captured text	4000
IDE_OTEL_CAPTURE_TOOL_INPUT_CONTENT	Include tool input content in logs	false
IDE_OTEL_CAPTURE_TOOL_DEFINITIONS	Include tool definitions in spans	false

OTel Logs

Variable	Description	Default
IDE_OTEL_ENABLE_LOGS	Enable OTel Logs signal export (OTLP)	true
IDE_OTEL_ENABLE_CONVERSATION_LOGS	Mirror span-first conversation facts as trace-correlated logs	false
IDE_OTEL_MCP_LOG_PAYLOAD	Include full MCP input/output payloads in logs	true
IDE_OTEL_LOG_ALL_EVENTS	Emit OTel log records for all hook events (not just MCP/shell/tool)	false
OTEL_EXPORTER_OTLP_LOGS_ENDPOINT	Override OTLP logs endpoint (auto-derived from traces endpoint if not set)	—

Resource Attributes

Variable	Description	Default
OTEL_RESOURCE_ATTRIBUTES	Comma-separated key=value pairs	—
IDE_OTEL_APP_NAME	Application name	ide-agent
IDE_OTEL_SUBSYSTEM_NAME	Subsystem name (Coralogix)	ide-hooks

Logging & Debug

Variable	Description	Default
IDE_OTEL_LOG_LEVEL	Log level (DEBUG, INFO, WARNING, ERROR)	WARNING
IDE_OTEL_LOG_FILE	Log file path	<hook-home>/otel_hook.log
IDE_OTEL_LOG_EVENTS	Log each hook event to file	false
IDE_OTEL_DEBUG_CONSOLE	Print spans to stdout (for debugging)	false

Advanced (Rarely Needed)

These settings have sensible defaults and typically don't need to be changed:

Variable	Description	Default
OTEL_EXPORTER_OTLP_INSECURE	gRPC only: true for plaintext, false for TLS	true
IDE_OTEL_DISABLE_BATCH	Disable OpenTelemetry batch processors and export immediately (useful for tests / short-lived debugging)	false
IDE_OTEL_STATE_TTL_SECONDS	TTL for state files before cleanup	86400
IDE_OTEL_STATE_CLEANUP_INTERVAL_SECONDS	Minimum interval between cleanup runs	3600
IDE_OTEL_STATE_LOCK_TIMEOUT_SECONDS	Max time to wait for state file locks	2
IDE_OTEL_HOOK_HOME	Override the hook's writable home directory (config, state, venv, log)	See below

IDE_OTEL_HOOK_HOME: When otel-hook runs from an installed package (i.e. the module lives inside site-packages), the hook automatically uses $XDG_DATA_HOME/opentelemetry-hooks (defaulting to ~/.local/share/opentelemetry-hooks) instead of the package directory, so all writable files are placed in a user-owned location. Set IDE_OTEL_HOOK_HOME to an absolute path to override this location explicitly (useful for project-local or shared deployments). When running from a source checkout or a directly-copied script, the directory that contains otel_hook.py is used as before.

Hook Stdout Response

The hook writes the response expected by the current harness.

• Default (backward compatible):

{"continue": true}

• Codex passive hooks (SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse):

<no stdout>

• Cursor permission hooks (preToolUse, subagentStart, beforeShellExecution, beforeMCPExecution, beforeReadFile, beforeTabFileRead) return the required observer response:

{"permission": "allow"}

• For events using the default response, if IDE_OTEL_LOCAL_SPANS is explicitly set (true or false), the response includes:

{"continue": true, "local_spans": true}

For the stdout response field, local_spans uses IDE_OTEL_LOCAL_SPANS when set; otherwise internal behavior falls back to IDE_OTEL_BATCH_ON_STOP. Codex responses are adapter-managed: passive non-Stop events skip stdout entirely. Codex responses and Cursor permission responses omit the custom local_spans field to respect their schemas.

Local Trace Files (Agent-Friendly)

When local trace saving is enabled, each hook event is also written to JSONL in:

• .cursor/hooks/opentelemetry-hook/.state/local_spans/<session_key>.jsonl
• .cursor/hooks/opentelemetry-hook/.state/local_spans/unscoped.jsonl (if no session key exists)

Each line is a single JSON object, for example:

{
  "timestamp_ns": 1771976482308258082,
  "event": "UserPromptSubmit",
  "ide": "copilot",
  "session_key": "agent-s1",
  "generation_key": null,
  "data": {
    "hook_event_name": "beforeSubmitPrompt",
    "session_id": "agent-s1",
    "prompt": "hello"
  }
}

MDM / Managed Configuration

For enterprise deployments, configuration can be pushed to developer machines via MDM (Mobile Device Management) systems such as Jamf, Intune, or Group Policy. MDM-managed settings override otel_config.json values but can still be overridden by environment variables.

Precedence (highest to lowest):

1. Environment variables
2. MDM-managed configuration (macOS plist / Windows registry)
3. otel_config.json file
4. Built-in defaults

macOS (Configuration Profile)

The hook reads managed preferences from the domain dev.o11y.opentelemetry-hook. Deploy a .mobileconfig profile via Jamf, Mosyle, or Apple Business Manager with the following payload:

<dict>
    <key>PayloadType</key>
    <string>dev.o11y.opentelemetry-hook</string>
    <key>OTEL_EXPORTER_OTLP_ENDPOINT</key>
    <string>https://otel-collector.corp.example.com:4317</string>
    <key>OTEL_EXPORTER_OTLP_PROTOCOL</key>
    <string>grpc</string>
    <key>OTEL_SERVICE_NAME</key>
    <string>corp-ide-agent</string>
    <key>IDE_OTEL_CAPTURE_TEXT</key>
    <string>false</string>
</dict>

The managed plist is read from:

• /Library/Managed Preferences/dev.o11y.opentelemetry-hook.plist (device-level)
• ~/Library/Managed Preferences/dev.o11y.opentelemetry-hook.plist (user-level fallback)

Windows (Registry / Group Policy)

The hook reads string values from the Windows registry under:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\OpenTelemetryHook

with a fallback to HKEY_CURRENT_USER. Deploy via Intune, Group Policy (ADMX), or any MDM that manages registry keys:

Registry Value Name	Type	Example
OTEL_EXPORTER_OTLP_ENDPOINT	REG_SZ	https://otel-collector.corp.example.com:4317
OTEL_SERVICE_NAME	REG_SZ	corp-ide-agent
IDE_OTEL_CAPTURE_TEXT	REG_SZ	false

Any key from the Configuration Reference can be set via MDM.

Backend Examples

Jaeger (Local Development)

docker run -d --name jaeger \
  -p 4317:4317 -p 4318:4318 -p 16686:16686 \
  jaegertracing/all-in-one:latest

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4317",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

View traces at http://localhost:16686

Jaeger + Local File Export

Send traces to Jaeger and save them as local JSONL files for agent analysis or offline inspection:

docker run -d --name jaeger \
  -p 4317:4317 -p 4318:4318 -p 16686:16686 \
  jaegertracing/all-in-one:latest

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4317",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true",
  "IDE_OTEL_LOCAL_SPANS": "true"
}

Traces are exported to Jaeger at http://localhost:16686 and simultaneously written to .state/local_spans/<session>.jsonl.

Local Files Only (No Backend)

Save spans as local JSONL files without sending to any remote backend. Useful for offline debugging, CI environments, or feeding traces back to an agent:

{
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true",
  "IDE_OTEL_LOCAL_SPANS": "true"
}

Omit OTEL_EXPORTER_OTLP_ENDPOINT to skip remote export. Spans are written to .state/local_spans/<session>.jsonl. Each line is a JSON object with trace/span IDs, attributes, and timing — see Local Trace Files for the format.

Coralogix

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "https://ingress.<region>.coralogix.com:443/v1/traces",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
  "OTEL_EXPORTER_OTLP_HEADERS": "authorization=Bearer%20<YOUR_API_KEY>",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

Replace <region> with your Coralogix domain (e.g., us1, eu1, ap1). If Coralogix requires cx.application.name, add it via OTEL_RESOURCE_ATTRIBUTES:

{
  "OTEL_RESOURCE_ATTRIBUTES": "cx.application.name=ide-agent"
}

Datadog

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4317",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

Requires the Datadog Agent with OTLP ingestion enabled.

Grafana / Tempo

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "https://otlp-gateway-<zone>.grafana.net/otlp",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
  "OTEL_EXPORTER_OTLP_HEADERS": "authorization=Basic%20<BASE64_CREDENTIALS>",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

Honeycomb

{
  "OTEL_EXPORTER_OTLP_ENDPOINT": "https://api.honeycomb.io",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
  "OTEL_EXPORTER_OTLP_HEADERS": "x-honeycomb-team=<YOUR_API_KEY>",
  "OTEL_SERVICE_NAME": "ide-agent",
  "IDE_OTEL_BATCH_ON_STOP": "true"
}

Hook fact contract and provider adapters

• Provider-specific payload interpretation lives behind Cursor, Windsurf, Claude, Codex, Gemini/Antigravity, Copilot, and OpenCode adapters. Every adapter produces the same typed canonical event, privacy-safe conversation/relationship facts, workspace identity, and explicit native context before lifecycle services receive a normalized dictionary.
• Spans are the authoritative/default signal. Prompt, assistant-response, stop-message, error, and delegation facts emit length plus SHA-256 metadata by default. Raw content requires IDE_OTEL_CAPTURE_CONVERSATION_CONTENT=true or the legacy IDE_OTEL_CAPTURE_TEXT=true; masking and truncation still apply.
• Optional conversation logs are disabled by default. IDE_OTEL_ENABLE_CONVERSATION_LOGS=true mirrors the normalized span facts as trace-correlated structured logs using the same hook event ID.
• Subagent callbacks preserve provider IDs or receive a session-persisted hook ID, emit parent_agent_id, correlate concurrent start/stop callbacks in FIFO order, and add delegation links when a valid start context is available. No-ID identical starts are kept as distinct invocations because suppressing them would discard legitimate concurrent agents; stable provider callback IDs remain idempotent.
• Workspace identity includes only observed workspace, working directory, repository root/name/owner, vcs.ref.head.name, and a SHA-256 of a credential-free normalized Git remote. The hook process's own current directory is not substituted when the event supplies no workspace evidence. Raw remotes are never emitted.
• Hook signals carry gen_ai.client.telemetry_source=hook and gen_ai.client.hook_schema_version=1. Native trace/span IDs are preserved and linked only when supplied through explicit native_trace_id, native_span_id, and optional native_parent_span_id fields (camelCase aliases are accepted). Generic trace_id / span_id fields remain upstream parent context and are never double-classified as native evidence. Native and hook telemetry are intentionally not deduplicated.

Cross-agent MCP and lifecycle contract

• Codex and Claude encoded names use mcp__<server>__<tool>. One bounded parser preserves the original gen_ai.client.tool_name and exports gen_ai.client.mcp_server plus gen_ai.client.mcp_tool; __ inside the tool portion is preserved. Parsing applies to pre, post, permission, and failure callbacks on both spans and logs.
• Cursor dedicated MCP callbacks use mcp_server_name and tool_name. mcp_server_name takes precedence over mcp_server and the executable command, so a command path cannot replace a real server identity.
• Cursor's stable generic tool_use_id owns the logical invocation. Session-backed FIFO correlation merges BeforeMCPExecution / AfterMCPExecution server, tool, duration, status, and result metadata into the matching generic pre/post callbacks. Cursor's dedicated duration value is milliseconds and is preserved as duration_ms. Batch mode folds correlated dedicated evidence into the buffered generic call; streaming mode emits dedicated lifecycle evidence spans (and logs when enabled) with the same ID and enriches the later generic post span. gen_ai.client.mcp.correlated_evidence=true distinguishes those callback spans from the logical generic tool span. Unmatched dedicated evidence is still emitted as a span without inventing an ID.
• Codex PermissionRequest reuses an open tool ID only when session, turn/generation, tool name, and event order identify one unambiguous invocation. Ambiguous permissions remain uncorrelated.
• Duplicate session, prompt, generation-stop, tool, error, subagent, compaction, and permission callbacks are suppressed with bounded session state. Stable IDs use event-plus-ID keys; no-ID callbacks use lifecycle-scoped fingerprints and short bounded windows. Legitimate calls across completed generation boundaries are preserved.
• Result size and digest are emitted as content-free metadata. Existing content gates remain unchanged: prompt capture is off by default, tool input content requires IDE_OTEL_CAPTURE_TOOL_INPUT_CONTENT, and MCP log payloads continue to follow IDE_OTEL_MCP_LOG_PAYLOAD.

Span Attributes

Common (All Spans)

Attribute	Description
gen_ai.client.hook.event	Canonical event name (PascalCase)
gen_ai.client.hook.event_id	Provider event ID or deterministic hook callback identity
gen_ai.client.telemetry_source / gen_ai.client.hook_schema_version	Explicit hook provenance and contract version
gen_ai.client.name	Canonical harness/engine identity (codex, cursor, copilot, claude, opencode, etc.); see Harness Detection
gen_ai.client.agent_engine	Inner agent engine when it differs from the outer harness (for example Cursor running Claude Code)
gen_ai.client.session_id	Session identifier
gen_ai.client.generation_id	Generation identifier (Cursor)
gen_ai.client.workspace	Workspace / working directory
gen_ai.client.cwd / gen_ai.client.repository_root	Event working directory and resolved repository root
vcs.repository.name / vcs.ref.head.name	Repository and Git branch identity
gen_ai.client.repository.remote.sha256	SHA-256 of the credential-free normalized Git remote
gen_ai.client.native_trace_id / gen_ai.client.native_span_id	Valid explicit native source identifiers; generic trace fields are reserved for upstream parenting
gen_ai.client.timestamp	Event timestamp (ISO 8601)
gen_ai.system	Deprecated legacy GenAI system/provider attribute retained for backward compatibility
gen_ai.operation.name	chat, execute_tool, or invoke_agent
telemetry.distro.name / telemetry.distro.version	Hook package provenance on the OTel resource and in the local JSON span's resource object. The version is resolved from installed package metadata rather than duplicated in hook logic; neither field overwrites agent service.name or service.version

GenAI (When Available)

Attribute	Description
gen_ai.provider.name	Canonical GenAI provider when inferred from payload/model metadata
gen_ai.request.model	Requested model name
gen_ai.response.model	Response model name
gen_ai.conversation.id	Session / conversation ID
gen_ai.usage.input_tokens	Input token count
gen_ai.usage.output_tokens	Output token count
gen_ai.usage.cache_creation.input_tokens	Cache-write input token count when provided
gen_ai.usage.cache_read.input_tokens	Cache-read input token count when provided
gen_ai.request.temperature	Temperature setting
gen_ai.request.max_tokens	Max tokens setting
gen_ai.request.choice.count	Requested number of choices/candidates
gen_ai.output.type	Requested output modality (text, json, image, speech)
gen_ai.agent.id / gen_ai.agent.name	Agent identity when the hook payload includes agent metadata
gen_ai.response.finish_reasons	Finish reasons array
gen_ai.system_instructions	System instructions (opt-in text capture)
gen_ai.input.messages	Input messages (opt-in)
gen_ai.output.messages	Output messages (opt-in)

Event-Specific

Event	Key Attributes
UserPromptSubmit	gen_ai.client.composer_mode, gen_ai.request.model
PreToolUse / PostToolUse	gen_ai.client.tool_name, gen_ai.client.tool_id, gen_ai.client.tool_use_id, gen_ai.client.duration_ms, and explicit MCP identity when encoded
PostToolUseFailure	gen_ai.client.tool_name, gen_ai.client.tool_use_id, gen_ai.client.status=error, privacy-safe error length/hash, and explicit MCP identity when encoded
BeforeShellExecution / AfterShellExecution	gen_ai.client.command, gen_ai.client.cwd, gen_ai.client.exit_code
BeforeMCPExecution / AfterMCPExecution	gen_ai.client.mcp_server, gen_ai.client.mcp_tool
BeforeReadFile / AfterFileEdit	gen_ai.client.file_path, gen_ai.client.edits
SubagentStart / SubagentStop	gen_ai.client.subagent_type, gen_ai.client.agent_id, gen_ai.client.parent_agent_id, ID source, delegation length/hash, and status
Stop	gen_ai.client.status, gen_ai.client.loop_count
ErrorOccurred	error.type, error.code, gen_ai.client.error.length, gen_ai.client.error.sha256, and gen_ai.client.is_interrupt

Real error and failure callbacks set the OpenTelemetry span status to ERROR without placing raw error content in the status description. Intentional callbacks marked is_interrupt=true retain UNSET status and use gen_ai.client.status=interrupted.

OTel Logs (MCP, Shell, Tool Events)

When IDE_OTEL_ENABLE_LOGS=true (default), the hook emits structured OpenTelemetry log records alongside traces. Log records are automatically correlated with the active span's trace context, so you can jump between traces and logs in your backend.

What gets logged

Event Type	Log Records	Payload Control
MCP calls (BeforeMCPExecution, AfterMCPExecution)	Always when logs enabled	IDE_OTEL_MCP_LOG_PAYLOAD
Shell execution (BeforeShellExecution, AfterShellExecution)	Always when logs enabled	IDE_OTEL_MCP_LOG_PAYLOAD
Tool usage (PreToolUse, PostToolUse, PostToolUseFailure)	Always when logs enabled	IDE_OTEL_CAPTURE_TOOL_INPUT_CONTENT
Conversation facts (prompt, response, stop message, error, delegation)	Only when IDE_OTEL_ENABLE_CONVERSATION_LOGS=true	IDE_OTEL_CAPTURE_CONVERSATION_CONTENT
All other events	Only when IDE_OTEL_LOG_ALL_EVENTS=true	—

MCP Log Attributes

Attribute	Description
gen_ai.client.mcp_server	MCP server name
gen_ai.client.mcp_tool	MCP tool name
gen_ai.client.mcp.input	Full input payload (opt-in)
gen_ai.client.mcp.input.length	Input payload size
gen_ai.client.mcp.input.sha256	Input payload hash
gen_ai.client.mcp.output	Full output payload (opt-in)
gen_ai.client.mcp.output.length	Output payload size
gen_ai.client.mcp.output.sha256	Output payload hash
gen_ai.client.mcp.duration_ms	MCP call duration
gen_ai.client.mcp.stdout	Server stdout (if available)
gen_ai.client.mcp.stderr	Server stderr (if available)

Endpoint Derivation

The logs endpoint is derived automatically:

1. If OTEL_EXPORTER_OTLP_LOGS_ENDPOINT is set, it's used directly
2. Otherwise, /v1/traces is replaced with /v1/logs in OTEL_EXPORTER_OTLP_ENDPOINT
3. For gRPC, the same endpoint serves all signals

Example: https://ingress.us1.coralogix.com:443/v1/traces → https://ingress.us1.coralogix.com:443/v1/logs

Session-level Batching

When IDE_OTEL_BATCH_ON_STOP=true (recommended):

1. SessionStart: Creates the persisted trace/session record once. Duplicate starts reuse the same trace and phantom parent and do not emit another root.
2. Generation events: Buffer to .state/batches/<generation_id>.jsonl. Explicit generation IDs and implicit fallback generations are both registered as session-owned pending batches, so Cursor sessions without UserPromptSubmit are still flushable.
3. Stop / StopFailure / Interrupt: Flushes the current generation exactly once and removes only that generation's pending/dedupe/correlation state. The session remains open; this is required for multi-prompt Codex and Claude sessions.
4. SessionEnd: Discovers and flushes every registered or on-disk batch owned by the session, then emits one gen_ai.client.session root. Batch, dedupe, correlation, and session state are removed after the authoritative trace flush succeeds. Logs are flushed and diagnosed independently, so a log-only exporter failure cannot replay spans that were already delivered.

For harnesses without a generation_id, the hook derives generation boundaries from UserPromptSubmit → Stop cycles. If a provider emits neither a prompt boundary nor a generation ID, the first generation-owned event creates an implicit fallback generation. Codex now registers SessionEnd and Interrupt. Bounded, idempotent stale-session finalization remains a fallback for sessions whose end callback never arrives.

Local JSON export routes spans by gen_ai.client.session_id, including roots emitted during stale-session finalization. A sessionless cleanup trigger therefore cannot move a stale root into unscoped.jsonl or copy it into another session's file.

When upstream context is present, hook spans keep the real trace_id and attach to the real upstream parent span. The hook still cannot force a specific emitted span_id for its own spans because the Python OpenTelemetry SDK assigns span IDs when spans are started.

Harness Detection

The hook identifies which harness is calling it:

Signal	Harness identity
Managed command source flag (otel-hook --cursor, --codex, --claude, etc.)	Preferred identity for setup-generated hooks
Legacy managed IDE_OTEL_HOOK_SOURCE env	Compatibility identity for older setup-generated hooks
IDE_OTEL_IDE_NAME env var	Explicit override for generic hook runners or manual debugging
Parent process tree (ps parent-chain walk)	Compatibility fallback for legacy/unmanaged hooks
Self-reported ide_name, client, or source_app values such as OpenAI Codex, Codex CLI, GitHub Copilot, GitHub Copilot CLI, GitHub Copilot Chat, Claude Code, Claude Code CLI, Anthropic Claude Code, Cursor IDE, Cursor CLI, Anti Gravity, Anti Gravity CLI, OpenCode / OpenCode CLI, Windsurf IDE, or Codeium Windsurf (case-insensitive, hyphen/space-insensitive)	Normalized to the canonical gen_ai.client.name
Native agent_action_name and trajectory_id	Windsurf / Cascade; checked before the Cursor ID heuristic
conversation_id or generation_id in input	Cursor
transcript_path, permission_mode, or notification_type	Claude Code
turn_id, tool_response, or last_assistant_message	Codex
session_id only (no Cursor-specific fields)	GitHub Copilot

Detection order is: (1) managed command source flag, (2) legacy managed source env, (3) explicit IDE_OTEL_IDE_NAME, (4) process-tree fallback, (5) self-reported payload fields, then (6) heuristics. Setup-generated hooks therefore do not depend on process-tree or ambient environment inference for their primary identity.

The hook still detects the outer wrapper harness/process, but the emitted canonical client identity usually prefers a distinct inner engine when one is present (for example Gemini running under Claude Code). In those cases, spans/resources use the inner engine for gen_ai.client.name and gen_ai.system, keep gen_ai.client.agent_engine for compatibility, and record the wrapper as gen_ai.client.wrapper. Cross-engine promotion is now gated on strong payload evidence (explicit engine fields, self-reported client identity, or corroborated semantic fields), so weak hints such as leaked wrapper env vars do not relabel Cursor events and create duplicate workspace-context telemetry for the same hook event. Native payload signals beat leaked wrapper-only env hints, so Cursor-specific fields such as conversation_id / generation_id still emit gen_ai.client.name=cursor when stale Claude-specific hints are present. When the hook can infer a provider from the payload, it also sets gen_ai.provider.name as the canonical provider attribute (v1.37+).

File Structure

.cursor/
├── hooks.json                          # Active Cursor hooks config (created by setup.sh)
└── hooks/
    └── opentelemetry-hook/
        ├── setup.sh                            # One-command setup (creates/merges hooks.json)
        ├── otel_hook.py                        # Main hook implementation (exposed as `otel-hook` when installed)
        ├── otel_config.json                    # Your config (gitignored, auto-created)
        ├── otel_config.example.json            # Config template
        ├── README.md                           # This file
        ├── examples/
        │   ├── hooks.example.json              # Full Cursor hooks template
        │   ├── cursor-hooks.example.json       # Minimal Cursor hooks template
        │   ├── copilot-hooks.example.json      # GitHub Copilot hooks template
        │   ├── claude-hooks.example.json       # Claude Code hooks template
        │   ├── claude-managed-settings.example.json # Minimal Claude managed-settings snippet
        │   ├── opencode-plugin.example.ts      # OpenCode plugin template
        │   └── antigravity-workflow.example.md # Antigravity workflow template
        ├── .gitignore                          # Excludes secrets, venv, state
        ├── .venv/                              # Python venv (auto-provisioned)
        └── .state/                             # Runtime state
            ├── sessions/                       # Session trace context
            └── batches/                        # Generation event buffers

Privacy & Security

What Gets Sent (by default)

• Event names and timing
• Tool/command names
• File paths
• Prompt, response, stop-message, error, and delegation length and SHA-256 hash (not content)

Opt-in Content Capture

Set IDE_OTEL_CAPTURE_CONVERSATION_CONTENT=true to include conversation and delegation text. IDE_OTEL_CAPTURE_TEXT=true remains a backward-compatible broader opt-in. Combine either with IDE_OTEL_MASK_PROMPTS=true to redact:

• Email addresses
• Long tokens / API keys
• macOS usernames from paths

Claude compaction instructions and summaries follow the same conversation-content gate. Tool-batch inputs/results are reduced to lengths and hashes before local buffering; IDE_OTEL_CAPTURE_TOOL_INPUT_CONTENT=true permits previews bounded by IDE_OTEL_TEXT_MAX_CHARS, with masking when enabled. This applies to newly received callbacks, not existing buffer files.

Never Sent

• API keys or credentials (automatically filtered)
• File contents (unless tool_response capture is enabled)
• Raw code

Troubleshooting

Run the doctor

otel-hook doctor
otel-hook doctor --agent codex --json

The doctor is read-only. It reports effective privacy booleans and sanitized exporter endpoints/failures; it never prints OTLP headers, credentials, telemetry payloads, or raw delivery-error messages. Exit status is 0 for healthy, 1 for degraded, and 2 for an invalid configuration/runtime failure.

Check the log

# pip/pipx install
tail -f ~/.local/share/opentelemetry-hooks/otel_hook.log

# source checkout / copied-source install
tail -f ./otel_hook.log

Enable debug output

{
  "IDE_OTEL_LOG_LEVEL": "DEBUG",
  "IDE_OTEL_DEBUG_CONSOLE": "true",
  "IDE_OTEL_LOG_EVENTS": "true"
}

Test manually

echo '{"hook_event_name":"SessionStart","session_id":"test-123"}' | otel-hook

For deterministic local export checks, disable the SDK batch processor for just the hook process:

printf '%s\n' '{"hook_event_name":"SessionStart","session_id":"test-123"}' | env IDE_OTEL_DISABLE_BATCH=1 otel-hook

This bypasses the SDK's background exporter only; IDE_OTEL_BATCH_ON_STOP still controls the hook's own session-level buffering.

Common issues

Problem	Fix
opentelemetry-sdk not installed	Auto-provisioning may still be in progress; wait ~30s and retry, or run .venv/bin/pip install opentelemetry-sdk opentelemetry-exporter-otlp
Missing API key	Set OTEL_EXPORTER_OTLP_HEADERS with your auth token in config
cx.application.name required	Coralogix needs this — set automatically, or add to OTEL_RESOURCE_ATTRIBUTES
Orphan spans	Enable IDE_OTEL_BATCH_ON_STOP=true for session-level traces
No traces appearing	Check endpoint, protocol, and auth headers in config. Verify the backend is running and reachable.
Wrong harness detected	Check the parent process chain and input payload first; for generic runners or debugging, set IDE_OTEL_IDE_NAME explicitly in the hook command
Traces going to the wrong backend	Verify OTEL_EXPORTER_OTLP_ENDPOINT points to the intended backend

Contributing

Contributions are welcome. To get started:

git clone https://github.com/o11y-dev/opentelemetry-hooks.git
cd opentelemetry-hooks
pip install -r requirements-dev.txt
python -m pytest tests/ -v

Please open an issue first if you plan a large change.

Credits

• Built on pure OpenTelemetry Python SDK
• Uses OpenTelemetry GenAI Semantic Conventions
• Supports GitHub Copilot hooks, Cursor IDE / CLI and Windsurf hook payloads, Claude Code hook payloads, and compatible runners such as OpenCode

License

MIT