Piping input into plugin eval now works because startup no longer captures that stdin first.
What's wrong with this entry?
Startup now recognises a plugin eval invocation, alongside the non-REPL subcommands and mcp serve, and skips capturing early stdin so the input reaches the eval run instead. Unconditional in the CLI entry path.
isPluginEvalInvocation
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.235
plugin evalnow tells you when a nearby plugin is not being loadedBoth mention eval
-
v2.1.235
--eval-diron the eval command, with warnings that name the fixBoth mention eval
-
v2.1.235
Eval setup refuses directories it cannot vouch for
Both mention eval