Non-interactive runs now accept and queue idle notices from peer sessions.
What's wrong with this entry?
The non-interactive entrypoint now watches its own session state, records which peers are idle, and queues incoming idle notices for the model, waking the loop the same way an incoming peer message does.
- Each notice and each recorded subscription is logged, including a count of subscriptions that arrived before the handler was mounted.
- No separate gate was found on this wiring.
enqueueIdleNoticesForModel
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.248
Wake routing and cross-session notices rewritten off UI effects
Both mention multi
-
v2.1.246
Multi-agent reply pairing now rejects and counts suspicious matches
Both mention multi
-
v2.1.239
Worker agents told to review, test, commit and report a PR link
Both mention multi