Clarify Langfuse credential preflight

This commit is contained in:
Annabell Schaefer
2026-07-28 13:23:54 +02:00
parent b2ef490839
commit e69bb9a1ae
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
{
"name": "langfuse",
"description": "Skills for working with Langfuse, the open-source LLM engineering platform for tracing, prompt management, and evaluation.",
"version": "1.4.3",
"version": "1.4.4",
"author": {
"name": "Langfuse",
"email": "support@langfuse.com"
+1 -1
View File
@@ -1,7 +1,7 @@
{
"name": "langfuse",
"displayName": "Langfuse",
"version": "1.4.3",
"version": "1.4.4",
"description": "Skills for working with Langfuse — the open-source LLM engineering platform for tracing, prompt management, and evaluation.",
"author": {
"name": "Langfuse",
+1 -1
View File
@@ -71,7 +71,7 @@ export LANGFUSE_SECRET_KEY=sk-lf-...
export LANGFUSE_BASE_URL=https://cloud.langfuse.com # example for EU cloud. For US cloud it's us.cloud.langfuse.com, and can also be a self-hosted URL. The server must always be specified in order to access Langfuse.
```
If `LANGFUSE_BASE_URL` is used instead of `LANGFUSE_HOST`, run `export LANGFUSE_HOST="$LANGFUSE_BASE_URL"`.
If not set, ask the user to set them in their shell or a `.env` file (do not ask them to paste keys into chat for security reasons). Keys are found in Langfuse UI → Settings → API Keys.
If not set, ask the user to set them in their shell or a `.env` file. Keys are found in the Langfuse project under Settings -> API Keys; the user should create a project API key pair there. If they do not have a Langfuse account yet, share that they can create one for free at `https://langfuse.com/cloud`. Do not ask them to paste keys into chat for security reasons.
### Detailed CLI Reference