OpenTelemetry observability for Claude Code sessions. Captures tool calls, LLM invocations, token usage, and errors as OTel traces.
Matches all tools
Hooks run on every tool call, not just specific ones
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
DATASETDash0 dataset name (optional)
${user_config.DATASET}OMIT_IOWhen true (default), omits prompt content and tool call inputs/outputs. Set to false to include full content.
${user_config.OMIT_IO}OTLP_URLDash0 OTLP endpoint URL (e.g. https://ingress.us1.dash0.com:4318)
${user_config.OTLP_URL}TEAM_NAMETeam name (optional). When set, all spans are tagged with the dash0.team.name attribute.
${user_config.TEAM_NAME}AGENT_NAMEAgent name, used as service.name (optional, defaults to claude-code)
${user_config.AGENT_NAME}AUTH_TOKENDash0 authentication token
${user_config.AUTH_TOKEN}OMIT_USER_INFOWhen true, hashes user.name and omits user.email. Default: false (real identity is sent).
${user_config.OMIT_USER_INFO}SHOW_SESSION_LINKWhen true, prints the session URL after every turn. Default: false (URL shown once at session start).
${user_config.SHOW_SESSION_LINK}Claude Code plugin that captures agent activity as OpenTelemetry traces — tool calls, LLM invocations, token usage, and errors.
/plugin install dash0@claude-plugins-official
If you get "Plugin not found in marketplace", the official marketplace may not be registered yet. Run
/plugin marketplace add anthropics/claude-plugins-officialfirst, then retry the install.
/plugin marketplace add dash0hq/claude-marketplace
/plugin install dash0-agent-plugin@dash0
The plugin is registered as
dash0in the official marketplace anddash0-agent-pluginin the Dash0 marketplace. Both install the same plugin; do not enable both at once or hooks will fire twice.
After installing, give the plugin your Dash0 credentials one of two ways. See Configuration for the full reference (all options, precedence, and env-var equivalents).
Find your exact otlp_url (and auth token) in your Dash0 org settings — the region segment varies (e.g. eu-west-1, us-west-2).
Config file (recommended) — create ~/.claude/dash0-agent-plugin.local.md (applies to all projects), or .claude/dash0-agent-plugin.local.md for a single project:
---
otlp_url: "https://ingress.<region>.aws.dash0.com"
auth_token: "your-dash0-auth-token"
dataset: "default"
---
Plugin UI — run /plugin → Installed → dash0 (or dash0-agent-plugin from the Dash0 marketplace — see the naming note above) → Configure, then /reload-plugins to apply.
If credentials are missing, you'll see this on session start:
dash0: telemetry is not active — configure the plugin to start sending data.
In environments without interactive access (containers, CI, scripts), use the CLI:
git config --global url."https://github.com/".insteadOf "[email protected]:"
claude plugin marketplace add dash0hq/claude-marketplace --scope user
claude plugin install dash0-agent-plugin@dash0 --scope user
Note: Claude Code downloads marketplace plugins via SSH by default. If SSH keys are not configured for GitHub, the
git configline above forces HTTPS. This is required in Docker containers, CI runners, or any environment without SSH access to GitHub.
This installs the plugin; configure credentials as in First-time setup.
Rolling the plugin out across many machines (MDM, golden image, dotfiles, config-management tooling) is two non-interactive steps: install the plugin, then give it credentials.
1. Install + enable with the non-interactive CLI shown in Headless / CI installation above (claude plugin marketplace add then claude plugin install … --scope user). The on-event binary is fetched from GitHub Releases on first run (checksum-verified), so each device needs outbound access to github.com and to your Dash0 ingress endpoint.
Hand-writing
~/.claude/settings.jsonis not enough to install the plugin.enabledPluginsonly enables an already-installed plugin andextraKnownMarketplacesonly registers the marketplace — neither downloads anything. Runclaude plugin install(above) to actually install it.
2. Supply credentials with any one of:
A config file at ~/.claude/dash0-agent-plugin.local.md — format in First-time setup, full options in Configuration file. The token is stored in cleartext, so chmod 600 it and keep it user-owned.
--config on the install command, which stores the token in the OS keychain (~/.claude/.credentials.json fallback on Linux) instead of cleartext:
claude plugin install dash0-agent-plugin@dash0 --scope user \
--config OTLP_URL=https://ingress.<region>.aws.dash0.com \
--config AUTH_TOKEN=<your-dash0-auth-token> \
--config DATASET=default
Values passed via
--configcan appear in shell history and process listings during provisioning — if that's a concern, use the config file or a secret manager instead.
Environment variables — DASH0_OTLP_URL plus CLAUDE_PLUGIN_OPTION_AUTH_TOKEN (and optionally DASH0_DATASET); see Environment variable fallback.
After credentials are in place, start a Claude Code session — you should see dash0: connected (v0.1.8).
# Test locally without marketplace
claude --plugin-dir /path/to/dash0-agent-plugin
# Build the binary locally (instead of downloading from GitHub Releases)
go build -o ~/.claude/plugins/data/dash0-agent-plugin-inline/bin/on-event-0.1.8-$(uname -s | tr '[:upper:]' '[:lower:]')-$(uname -m | sed 's/x86_64/amd64/') ./cmd/on-event/
npx claudepluginhub anthropics/claude-plugins-official --plugin dash0OpenTelemetry skills and reference documentation for AI coding assistants
dash0hqConsult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex and gemini CLIs when installed) to get diverse perspectives on coding problems
hex20 SEO/GEO skills and 5 commands on one shared contract for keyword research, content creation, technical audits, schema markup, monitoring, quality gates, entity truth, and campaign memory.
aaron-he-zhuComplete AI coding workflow system. Self-correcting memory + persistent FTS5-indexed research wikis + auto-research loop + multi-LLM council on a single SQLite store. 33 skills, 8 agents, 22 commands, 37 hook scripts across 24 events. Cross-agent via SkillKit.
rohitg00Production-grade academic research pipeline for Claude Code: research → write → review → revise → finalize. 4 skills, 27 modes, 39-agent ensemble, v3.7.3 + v3.8 L3 claim-faithfulness gate, v3.9.0 cross-index triangulation, v3.10 triangulation policy layer, v3.11 deterministic citation verification gate (#182).
Imbad0202