{"version":"2.1.292","anchor":"remote-bridge-caps-subagent-frames-queued-during-a-flush","canonical_anchor":"remote-bridge-caps-subagent-frames-queued-during-a-flush","heading":"Remote Control drops the oldest subagent updates when too many queue up","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-bridge-caps-subagent-frames-queued-during-a-flush","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Remote Control drops the oldest subagent updates when too many queue up\n\nIn Remote Control sessions, queued subagent updates are now capped, and the oldest are dropped when too many pile up\n\n**What**\n\nIn a session connected through Remote Control, messages that wait while earlier ones are still being sent now go into a capped queue. If more than a set number of updates from subagents (helper agents Claude starts to handle part of a task) pile up, the oldest are dropped until the queue empties.\n\nIf the cap itself fails, the failure is caught and written to the log.\n\n**Why**\n\nIn Remote Control sessions with a lot of subagent activity, older subagent updates can now be lost without any notice, for example after a reconnect.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}