migrate-to-langfuse
Migrate to Langfuse
You are running a one-off vendor switch to Langfuse. Interview first, plan second, execute only after confirmation. Never implement from memory — fetch the current Langfuse docs listed below at execution time.
1. Interview (always, before any code)
Ask only what you cannot detect. Inspect the repo first: dependencies and imports usually reveal the source platform (langsmith, arize, phoenix, braintrust, openinference, old langfuse pins).
- Source — which platform and version? Cloud or self-hosted? What access exists: API keys, a database connection, or only the application repo?
- Destination — Langfuse Cloud (which region) or self-hosted? Verify credentials by presence only (e.g.
[ -n "$LANGFUSE_SECRET_KEY" ]); never ask for secrets in chat, and never access.envcontents or key values by any means — no shell commands that echo them, no reading.envwith file tools, no grepping for values. Detect which variable names are set, nothing more. - Scope — which of: live tracing cutover, historical traces (including their scores, score configs, and custom model definitions), datasets, prompts, evaluators/LLM judges, experiment code. For history: everything or from a cutoff date? Ask what else exists in the source account (dashboards, alerts, annotation queues, saved views, ...). The repo cannot reveal server-side assets. Anything outside the supported list above is not covered by this skill: name it in the scope table as such, so the user plans to recreate it manually instead of discovering the gap after cutover.
- Mode — plan only (a written runbook) or execute?
If the request contradicts the repository (it names a platform that is not present, or asks to upgrade an SDK that is not installed), stop and reconcile with the user first — never reinterpret the request as a different migration and start executing it.
Present the resulting plan (scope table plus order of operations) and get the user's confirmation before changing any file. However imperative the request sounds, it does not authorize removing or replacing the existing vendor's instrumentation before the plan is confirmed.