fix(issues): expose actions, proposed_examples, and traces in issues list --format json#144
Merged
Merged
Conversation
`issueToMap` was omitting the `actions` field (evaluator spec) and `traces` field (linked evidence runs) from the JSON output of `project issues list` and `project issues update`. Agents reading the issues list couldn't see the existing evaluator, so they had no way to run new evidence traces against it or update the evaluator when it no longer covered a newly-linked trace. Both fields are now included when non-empty, decoded from raw JSON so they appear as structured objects rather than escaped strings. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Andy Young (ayoung19)
approved these changes
May 28, 2026
Add proposed_examples (per-trace regression example assertions) to issueToMap so agents can read existing assertions alongside the evaluator spec (actions) and linked traces. Symmetric with the evaluator read→test→update loop: agents can now read what assertions already exist for a trace, re-derive from the trace evidence, and re-propose if they have concretely better ground truth. The backend upserts on (issue_id, run_id) conflict, so re-running propose overwrites rather than ignoring. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Palash Shah (Palashio)
changed the title
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
2 participants
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.
Summary
issueToMapwas stripping three fields agents need to read and update issues effectively:actions— the evaluator spec; needed to test the existing evaluator against new traces and update it if the pattern has changedproposed_examples— per-trace regression example assertions; needed to see what assertions already exist and re-propose with better ground truth when availabletraces— linked evidence runs; needed to sample existing traces for evaluator regression checksAll three are now included when non-empty, decoded from raw JSON so they appear as structured objects.
Why this matters: The companion langchainplus PRs teach the issues agent a read→test→update loop for both evaluators and regression examples, symmetric with how it already reads and updates issue descriptions. Without these fields in the CLI output, agents can't see what already exists before deciding whether to update.
Related langchainplus PRs:
Test Plan
langsmith project issues list --project <name> --format jsonincludesactions,proposed_examples, andtraceson issues that have themRelease Note
none