🔧 Improve HUD eval script: auto-discover .env and simplify usage #419
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.
This PR updates the hud_eval_examples.py script to make running HUD evaluations simpler and more robust:
Path-agnostic .env discovery: replaced hardcoded .env path with find_dotenv, allowing the script to automatically locate the nearest .env in the repo hierarchy.
Environment validation: script now raises a clear error if HUD_API_KEY is missing instead of failing silently.
Minimal HUD eval flow: removed Docker/local setup references—script focuses only on running HUD evaluations with run_full_dataset.
Improved UX: users can place .env at the repo root (or export vars in their shell) and run the example from any directory without manual copying.
This change reduces setup friction and ensures consistent results across different environments.