Support explicit harness field in agent traces#8127
Open
jedisct1 wants to merge 1 commit intohuggingface:parse_agent_tracesfrom
Open
Support explicit harness field in agent traces#8127jedisct1 wants to merge 1 commit intohuggingface:parse_agent_tracesfrom
jedisct1 wants to merge 1 commit intohuggingface:parse_agent_tracesfrom
Conversation
When present, the harness field takes priority over type-value heuristics. This allows agents to self-identify even when their trace structure and type values collide with an existing harness like claude_code.
lhoestq
approved these changes
Apr 10, 2026
Member
lhoestq
left a comment
lhoestq
left a comment
There was a problem hiding this comment.
lgtm ! cc @cfahlgren1 it should be ok ?
Author
|
For a concrete example, https://huggingface.co/datasets/jedisct1/agent-traces-swival currently shows |
is there any parsing issues from the actual traces, or more about just the name of the harness? |
Author
|
@cfahlgren1 No parsing issues. This is just about showing the correct harness name. |
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
3 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.
Hi!
This small PR allows an optional
harnessfield to be parsed.When present, the harness field takes priority over type-value heuristics.
This allows agents to self-identify even when they contain property names that collide with an existing harness ("session", "system", etc.)