You'll notice
Useful2 Signal2
Eval runs refuse to write into a results directory that already existed.
What's wrong with this entry?
Anonymous. No account, no email.
--output-dir
What
When results go to the default location rather than one given with --output-dir, the tool now verifies the directory it just created is new and fails if a directory of that name already existed, instead of writing into whatever was there.
Evidence
results directory ${Se} already existed — a default results directory is always new; refusing to write into it
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Assistant messages built from streamed text now report a stop reason
Both mention output
-
v2.1.235
Eval results written inside a plugin warn that they may load as components
Both mention output
-
v2.1.238
Files changed during a turn are uploaded to the cloud session worker
Both mention output