Langfuse Upgrade MigrationSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Install
Commands as the repository documents them. They are shown, not run.
npm info @langfuse/client version
npm info @langfuse/tracing version
npm info langfuse version
npm install @langfuse/client @langfuse/tracing @langfuse/otel @opentelemetry/sdk-node
npm install [email protected] # Previous version
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: langfuse-upgrade-migration description: 'Upgrade Langfuse SDK versions and migrate between API changes. Use when upgrading Langfuse SDK, handling breaking changes, or migrating between Langfuse versions. Trigger with phrases like "upgrade langfuse", "langfuse migration", "update langfuse SDK", "langfuse breaking changes", "langfuse version". ' allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(pip:*) version: 1.17.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - langfuse - api - migration compatibility: Designed for Claude Code --- # Langfuse Upgrade & Migration ## Current State !`npm list langfuse @langfuse/client @langfuse/tracing @langfuse/otel 2>/dev/null | head -10 || echo 'No langfuse packages found'` !`pip show langfuse 2>/dev/null | grep -E "Name|Version" || echo 'Python langfuse not installed'` ## Overview Step-by-step guide for upgrading the Langfuse SDK across major versions. Covers v3 to v4 (OTel rewrite), v4 to v5, breaking changes, and automated codemods. ## Prerequisites - Existing Langfuse integration - Test suite covering traced operations - Git branch for the upgrade ## Version Roadmap | SDK | Package | Architecture | Status | |-----|---------|-------------|--------| | v3 | `langfuse` (single) | Custom, `Langfuse` class | Legacy | | v4 | `@langfuse/client`, `@langfuse/tracing`, `@langfuse/otel` | OpenTelemetry-based | Stable | | v5 | `@langfuse/client`, `@langfuse/tracing`, `@langfuse/otel` | OpenTelemetry + improvements | Latest | ## Instructions ### Step 1: Check Current Version and Plan ```bash set -euo pipefail # Check what you have npm list langfuse @langfuse/client @langfuse/tracing 2>/dev/null # Check latest available npm info @langfuse/client version npm info @langfuse/tracing version npm info langfuse version # Python pip show langfuse 2>/dev/null | grep Version pip index versions langfuse 2>/dev/null | head -3 ``` ### Step 2: v3 to v4 Migration (TypeScript) This is the biggest migration -- v4 rewrites tracing on OpenTelemetry. **2a. Install new packages:** ```bash set -euo pipefail # Install v4+ packages npm install @langfuse/client @langfuse/tracing @langfuse/otel @opentelemetry/sdk-node # Keep langfuse v3 temporarily for comparison # Remove after migration: npm uninstall langfuse ``` **2b. Update initialization:** ```typescript // BEFORE (v3): import { Langfuse } from "langfuse"; const langfuse = new Langfuse({ publicKey: process.env.LANGFUSE_PUBLIC_KEY, secretKey: process.env.LANGFUSE_SECRET_KEY, baseUrl: process.env.LANGFUSE_HOST, }); // AFTER (v4+): import { LangfuseClient } from "@langfuse/client"; import { LangfuseSpanProcessor } from "@langfuse/otel"; import { NodeSDK } from "@opentelemetry/sdk-node"; // OTel setup (once at entry point) const sdk = new NodeSDK({ spanProcessors: [new LangfuseSpanProcessor()], }); sdk.start(); // Client for prompts, datasets, scores const langfuse = new LangfuseClient(); ``` **2c. Update tracing calls:** ```typescript // BEFORE (v3): Manual trace/span/generation const trace = langfuse.trace({ name: "my-op", input: data }); const span = trace.span({ name: "step-1", input: data }); await doWork(); span.end({ output: result }); const gen = trace.generation({ name: "llm", model: "gpt-4o" }); gen.end({ output: response, usage: { promptTokens: 10 } }); await langfuse.flushAsync(); // AFTER (v4+): startActiveObservation with auto-nesting import { startActiveObservation, updateActiveObservation } from "@langfuse/tracing"; await startActiveObservation("my-op", async () => { updateActiveObservation({ input: data }); await startActiveObservation("step-1", async () => { updateActiveObservation({ input: data }); const result = await doWork(); updateActiveObservation({ output: result }); }); await startActiveObservation({ name: "llm", asType: "generation" }, async () => { updateActiveObservation({ model: "gpt-4o" }); const response = await callLLM(); updateActiveObservation({ output: response, usage: { promptTokens: 10 } }); }); }); ``` **2d. Update OpenAI wrapper:** ```typescript // BEFORE (v3): import { observeOpenAI } from "langfuse"; // AFTER (v4+): import { observeOpenAI } from "@langfuse/openai"; // npm install @langfuse/openai ``` **2e. Update environment variable:** ```bash # BEFORE: LANGFUSE_HOST or LANGFUSE_BASEURL # AFTER: LANGFUSE_BASE_URL (LANGFUSE_BASEURL still works in v4 but not v5) ``` **2f. Update prompt management:** ```typescript // BEFORE (v3): const prompt = await langfuse.getPrompt("my-prompt", 2); // version as positional arg // AFTER (v4+): const prompt = await langfuse.prompt.get("my-prompt", { version: 2, // version in options object type: "text", // explicit type }); ``` **2g. Update shutdown:** ```typescript // BEFORE (v3): await langfuse.shutdownAsync(); // AFTER (v4+): await sdk.shutdown(); // Shuts down OTel SDK + flushes spans ``` ### Step 3: Python SDK Migration (v2 to v3) ```python # BEFORE (v2): from langfuse import Langfuse langfuse = Langfuse() @langfuse.observe() def my_function(): pass # AFTER (v3): from langfuse.decorators import observe, langfuse_context @observe() def my_function(): langfuse_context.update_current_observation( metadata={"key": "value"} ) ``` ### Step 4: Run Tests and Verify ```bash set -euo pipefail # Run existing test suite npm test # Verify traces appear in dashboard node -e " const { startActiveObservation, updateActiveObservation } = require('@langfuse/tracing'); startActiveObservation('upgrade-verify', async () => { updateActiveObservation({ input: { test: true }, output: { migrated: true } }); }).then(() => console.log('Migration verified')); " ``` ### Step 5: Remove Old Package ```bash set -euo pipefail # After all tests pass npm uninstall langfuse # Verify no lingering imports grep -rn "from ['\"]langfuse['\"]" src/ || echo "No old imports found" ``` ## Breaking Changes Quick Refere
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__langfuse-upgrade-migration.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Langfuse Upgrade Migration skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Langfuse Upgrade Migration safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Langfuse Upgrade Migration access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Langfuse Upgrade Migration work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.