docs: clarify that trace queries should use observations endpoint - #95
Merged
Lotte-Verheyden merged 2 commits intoAug 12, 2026
Merged
Conversation
|
@claude review |
Member
Author
|
@claude review |
Lotte-Verheyden
deleted the
lfe-14573-clarify-that-traces-should-use-observations-api-v2
branch
August 12, 2026 21:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users almost always describe their data as "traces," but the modern query endpoint in the CLI and API is
observations, nottraces. Thetracesendpoints are outdated. This updates the CLI reference tip so agents default toobservationseven when a request is phrased in terms of traces.Bumps both plugin manifests
1.5.2→1.5.3(patch, in lockstep) for the skill-content clarification.Note
Low Risk
Docs and version metadata only; no runtime or API behavior changes.
Overview
Documentation update so agents and users route trace-style questions through the modern
observationsCLI/API instead of deprecatedtracesendpoints.The CLI reference Tips section now states to always use
observations(optionally with--trace-idfor a known trace), replacing the narrower note abouttraces listtimeouts on Langfuse Cloud. Plugin manifests for Claude and Cursor are bumped 1.5.2 → 1.5.3 in lockstep for this skill-content change.Reviewed by Cursor Bugbot for commit f55ccc4. Bugbot is set up for automated code reviews on this repo. Configure here.