Headless runs can sync a worker directory before and after each turn, if the host provides a callback.
A per-turn sync callback in the headless loop is accepted but nothing in the CLI supplies one.
What's wrong with this entry?
The headless streaming loop accepts an optional callback that runs before each turn and again after it, receiving the message IDs from that turn. It only runs when the embedding caller supplies one, and nothing in the CLI itself does.
workerDirSync
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.246
Non-interactive runs retry a response that was cut off mid-stream
Both mention headless mode
-
v2.1.246
Headless idle detection now waits for background tasks and undelivered notifications
Both mention headless mode
-
v2.1.246
Headless runs no longer report themselves busy while blocked on a prompt
Both mention headless mode