You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
REPLArea: what it touches
New FeaturesKind: in v2.1.234,
New FeaturesSection of the release
What
Starting an asynchronous REPL evaluation now returns an evaluation id and the current queue depth, and when the evaluation finishes its output is inserted back into the conversation instead of being lost. Dispatching more than the per-context queue cap allows is rejected outright.
Details
The settled output arrives as a repl-eval element, after hooks have had a pass at it.
Output is truncated to a byte budget, cut on a UTF-8 character boundary so multi-byte text is not split.
If a hook blocks the output, it is withheld with that fact recorded rather than silently dropped.
repl_async_settle telemetry separates the withheld case, the hook-failed-open case and the case where the result never reached the conversation.
Evidence
async REPL dispatch rejected: queue depth cap
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
