feat: add one-per-thread trace listing#145
Draft
Paarth Ahuja (paarth-a) wants to merge 1 commit into
Draft
Conversation
7e18d5a to
354b47b
Compare
354b47b to
f9f1407
Compare
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.
Adds
--one-per-threadtolangsmith trace list. The command already queries root runs (is_root=true), so this flag asks the server to return at most one matching root run, i.e. trace, per non-emptythread_id; unthreaded traces remain individually listed.Linear: LSEN-32
Release Note
Add
--one-per-threadtolangsmith trace listto request one trace per conversation thread.Test Plan
one_per_threadrequest body behavior.mise exec go@1.25.9 -- go test ./internal/cmdmise exec go@1.25.9 -- go test ./...