The headless bridge now publishes whether it is running so other code can just ask.
What's wrong with this entry?
The bridge used by print and headless runs now publishes a liveness check on the session registry, so other code can ask directly whether the bridge is running rather than inferring it from side effects.
- The check reports whether the bridge's transcript writer exists.
remoteBridgeLive
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.219
Headless text output recovers the last full assistant message on an incomplete run
Both mention headless mode
-
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