Eval results saved inside a plugin now warn they might get loaded as plugin components.
What's wrong with this entry?
When results go under the plugin because no --output-dir was given, the command compares the destination against the plugin's layout and warns that files written there may be picked up as plugin components, pointing at --output-dir.
- Case discovery refuses symlinked directories.
- A directory with no prompt.md or case.yaml is logged and scanned for cases rather than treated as one.
files written there may be loaded as plugin components; pass --output-dir to write elsewhere
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.238
Files changed during a turn are uploaded to the cloud session worker
Both mention output
-
v2.1.248
Detection of "I'll check back later" phrasing in model output
Both mention output