Conversation
…ced templates When a workspace is defined via a file reference, hook commands with no explicit cwd now resolve relative to the workspace file's directory instead of the eval file's directory. This makes file-referenced templates self-contained — the same template produces identical behavior regardless of which eval file references it. Closes #1080 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying agentv with
|
| Latest commit: |
6926e8b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3d4c5dab.agentv.pages.dev |
| Branch Preview URL: | https://fix-1080-hook-cwd-workspace.agentv.pages.dev |
Red/Green UATSetupDirectory structure: The template uses Red (main) — nested eval failsThe hook's cwd defaulted to Root eval on main: ✅ (cwd happened to be at the right depth — Green (fix branch) — both evals passBoth evals now use (Scores are 0% as expected with |
Summary
When a workspace is defined via a file reference (e.g.,
workspace: .templates/eval-workspace-setup.yaml), hook commands with no explicitcwdnow resolve relative to the workspace file's directory instead of the eval file's directory.This makes file-referenced templates self-contained — the same template produces identical behavior regardless of which eval file references it.
workspaceFileDirtoWorkspaceConfig— set when workspace is resolved from a file referenceworkspaceFileDirtoScriptExecutionContext— passed through from workspace configconfig.cwd→context.workspaceFileDir→context.evalDirworkspaceFileDirinmergeWorkspaceConfigsCloses #1080
Test plan
workspaceFileDirtakes priority overevalDirwhen no explicitcwdis setcwdstill overridesworkspaceFileDirworkspaceFileDiris set for file references and undefined for inline configs🤖 Generated with Claude Code