You'll notice
Useful3 Signal2
Agent wake-ups and cross-session notices now run outside the render loop, with the same behaviour.
What's wrong with this entry?
Anonymous. No account, no email.
What
The machinery that wakes agents and batches cross-session notices no longer runs as render effects; it is now plain subscriptions with coalesced updates and explicit teardown, tracking its own in-flight work per agent instead of re-evaluating on every render. Existing warnings and drop/resume behaviour are unchanged.
Evidence
[wakeRouter] resume state error for
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.236
Headless sessions accept idle notices from peers
Both mention multi
-
v2.1.236
A new remote flag, on by default, controls message-input split repair
Both mention multi
-
v2.1.236
Every session now advertises that it can send idle notices
Both mention multi