{"version":"2.1.293","anchor":"remembered-reads-capped-silently-returns-dropped-count","canonical_anchor":"remembered-reads-capped-silently-returns-dropped-count","heading":"Queued messages tag monitor output, and remembered reads report how many were dropped","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remembered-reads-capped-silently-returns-dropped-count","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Queued messages tag monitor output, and remembered reads report how many were dropped\n\nQueued messages now mark whether they carry monitor output or a notice, and the cap on remembered reads returns a dropped count instead of logging it\n\n**What**\n\nQueued messages are messages waiting to be handed to Claude, such as output from a monitor that watches something running in the background.\n\n- A queued message tied to a watch now carries `monitorEvent`, holding the watch id and a kind: \"notice\" for housekeeping messages and \"output\" otherwise.\n\n- The record of a delivered queued message gains `monitor_event_count` and `monitor_event_chars`.\n\n- The helper that limits how many remembered file reads are kept no longer logs `remembered_read_dropped` itself. It now returns the kept reads together with a count of how many were dropped. One finding reports dropped reads still being logged under that name, so the logging appears to have moved to the code that calls the helper.\n\n- Home-seed announcements now record how late the read was.\n\n**Why**\n\nMonitor output can now be told apart from other messages slipped into the conversation. Most of the rest changes what is measured rather than what you see.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}