fix: prefer multilevel demo files over plain .txt in eval scripts#103
Merged
Conversation
When both {task_id}_multilevel.txt and {task_id}.txt exist in the demo
directory, all demo file lookup paths now prefer the multilevel (Option D)
format. Falls back to plain .txt, then .json for backwards compatibility.
Files changed:
- scripts/run_dc_eval.py
- scripts/run_eval_pipeline.py
- openadapt_evals/benchmarks/cli.py (_suite_find_demo)
- openadapt_evals/benchmarks/comparison_viewer.py
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
{task_id}_multilevel.txtand{task_id}.txtexist, all demo lookup paths now prefer the multilevel (Option D) format.txt, then.jsonfor backwards compatibilityrun_dc_eval.py,run_eval_pipeline.py,cli.py(_suite_find_demo),comparison_viewer.pyContext
The rigid plain-text demo format caused DC agents to abandon tasks when UI state didn't match descriptions. The multilevel format (PLAN + {Think, Action, Expect} + "adapt if needed") avoids this.
Test plan
{id}.txtand{id}_multilevel.txtpresent, multilevel file is selected{id}.txtpresent, falls back correctly{id}.jsonpresent, falls back correctly🤖 Generated with Claude Code