Trace hook-backed Claude Code sessions to Langfuse — turns, generations, tool calls, and token usage — with zero code changes.
claude plugin marketplace add langfuse/Claude-Observability-Plugin
claude plugin install langfuse-observability@langfuse-observabilityThe marketplace command registers the plugin marketplace and refreshes its local cache. The install command enables the plugin for your Claude Code user scope.
Restart Claude Code after install so the hook configuration is loaded.
Then configure the plugin from within a Claude Code session. This is a Claude Code slash command, not a shell command:
/plugin configure langfuse-observability@langfuse-observability
Alternatively, pass configuration values during install:
claude plugin install langfuse-observability@langfuse-observability \
--config LANGFUSE_PUBLIC_KEY=pk-lf-... \
--config LANGFUSE_SECRET_KEY=sk-lf-... \
--config LANGFUSE_BASE_URL=https://cloud.langfuse.comThe plugin requires or accepts:
| Field | Description |
|---|---|
LANGFUSE_SECRET_KEY |
Your Langfuse secret key (sk-lf-...). Stored in your OS keychain. |
LANGFUSE_PUBLIC_KEY |
Your Langfuse public key (pk-lf-...). |
LANGFUSE_BASE_URL |
https://us.cloud.langfuse.com (default), https://cloud.langfuse.com for EU, or your self-hosted URL. |
LANGFUSE_USER_ID |
Optional. User identifier attached to every trace (shown as the user in Langfuse). |
CC_LANGFUSE_DEBUG |
Verbose logging to ~/.claude/state/langfuse_hook.log. |
CC_LANGFUSE_MAX_CHARS |
Truncate captured inputs/outputs to this many characters (default 20000). |
CC_LANGFUSE_SKILL_TAGS |
Tag traces with skill:<name> for every skill invoked in the turn (default true). |
CC_LANGFUSE_CAPTURE_SKILL_CONTENT |
Include injected skill instruction text in the Skill tool span output (default false). |
Get keys from your Langfuse project settings → API Keys.
One of:
- uv (recommended) on
PATH. The hook usesuv run --scriptand installs the Langfuse SDK from the script metadata automatically. - Python 3.10+ as
python3withlangfuse>=4.0,<5installed in that Python environment. This is only used as a fallback whenuvis not onPATH.
If neither is set up, the hook exits silently — no impact on Claude Code.
A hook reads the session transcript incrementally on every turn (Stop) and at session end (SessionEnd), and emits a Langfuse trace with one span per turn, nested generations per assistant message, and child tool spans for every tool call. Token usage is captured when present.
The plugin observes only data that Claude Code exposes through hooks and transcript files.
Captured:
- Claude Code CLI sessions
- Claude Code GUI Code mode sessions
Not captured:
- Regular Claude Desktop Chat mode conversations
If you use the desktop app, switch to Code mode for hook-backed tracing. Regular Chat mode does not invoke Claude Code Stop or SessionEnd hooks and does not write the transcript file this plugin reads.
State is kept in ~/.claude/state/langfuse_state.json so re-runs only emit new turns.
This plugin transmits your Claude Code session data — conversation turns, assistant
generations, tool calls, and token-usage statistics — to the Langfuse endpoint you
configure (LANGFUSE_BASE_URL, default https://us.cloud.langfuse.com; EU and
self-hosted endpoints are supported). Data is sent at the end of each turn (the
Stop hook) and at session end (SessionEnd) using the Langfuse API keys you
provide, which are stored in your OS keychain. No data is sent anywhere other than
the endpoint you configure.
For how Langfuse Cloud handles data it receives, see the Langfuse privacy policy: https://langfuse.com/privacy . When using a self-hosted Langfuse instance, your data stays within your own infrastructure.
In Claude Code, run:
/plugin configure langfuse-observability@langfuse-observability
To stop tracing for new Claude Code CLI sessions and new Claude Code GUI Code mode sessions, disable the plugin:
claude plugin disable langfuse-observability@langfuse-observability --scope user
claude plugin listclaude plugin list should show the plugin as disabled. This keeps the plugin installed and does not delete your configuration.
To enable tracing again:
claude plugin enable langfuse-observability@langfuse-observability --scope userIf a Claude Code session is already running, restart it after disabling the plugin. Running sessions may have loaded their hooks at startup, so disabling the plugin is intended for new sessions.
claude plugin uninstall langfuse-observability- Nothing in Langfuse: check
~/.claude/state/langfuse_hook.log(enableCC_LANGFUSE_DEBUG). - Desktop chat has no traces: regular Claude Desktop Chat mode is not hook-backed. Use the
claudeCLI or Claude Code GUI Code mode. - Hook not firing: confirm with
claude plugin listthat langfuse-observability is enabled; restart Claude Code. - langfuse import errors (no uv): install uv, or ensure the
python3on your PATH is Python 3.10+ and haslangfuse>=4.0,<5installed.
MIT