Problem
During agent-lab R305, Terminal-Bench live scoring needed to point @tangle-network/agent-bench at an existing venv:
TERMINAL_BENCH_VENV=/home/drew/code/agent-runtime/bench/.venv-terminal-bench
The adapter treated that absolute path as relative to the package bench root, so preflight failed until I created a local symlink at:
node_modules/@tangle-network/agent-bench/.venv-terminal-bench -> /home/drew/code/agent-runtime/bench/.venv-terminal-bench
Expected
If TERMINAL_BENCH_VENV is absolute, use it as-is.
If it is relative, resolve it against the existing bench root.
Why it matters
Agent-lab and product eval worktrees should be able to reuse a known-good Terminal-Bench venv without mutating node_modules or relying on symlinks.
This is a small adapter robustness fix, not a change to scoring semantics.
Observed in
Problem
During agent-lab R305, Terminal-Bench live scoring needed to point
@tangle-network/agent-benchat an existing venv:The adapter treated that absolute path as relative to the package bench root, so preflight failed until I created a local symlink at:
Expected
If
TERMINAL_BENCH_VENVis absolute, use it as-is.If it is relative, resolve it against the existing bench root.
Why it matters
Agent-lab and product eval worktrees should be able to reuse a known-good Terminal-Bench venv without mutating
node_modulesor relying on symlinks.This is a small adapter robustness fix, not a change to scoring semantics.
Observed in
@tangle-network/agent-bench 0.1.0via agent-lab install