{"version":"2.1.293","anchor":"monitor-watch-close-telemetry","canonical_anchor":"monitor-watch-close-telemetry","heading":"Monitor watches report why they closed, plus a fixed MCP app sandbox host","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/monitor-watch-close-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Monitor watches report why they closed, plus a fixed MCP app sandbox host\n\nMonitor watches now emit a close event saying why they stopped, and a fixed MCP app sandbox host was added\n\n**What**\n\nA monitor watch is Claude Code following the output of a running command. When a watch closes it now emits `monitor_watch_closed`. The event records `closed_by`, which is one of `too_much_output`, `flushed`, `dropped` or `exited`. It also records how many events were queued and how many were suppressed. The name was added to a list of event names, and it is emitted from one more place that was not read.\n\nIn the same area of code, a new constant `MCP_APP_SANDBOX_BASE_HOST` is set to `sandbox.claudemcpcontent.com`. It sits next to the existing wildcard host `*.claudemcpcontent.com`. MCP apps are add-ons served through MCP servers, and this host is where their sandboxed content is loaded from.\n\n**Why**\n\nThe close event is reporting only and does not change what you see. The new host constant points to MCP app content using one fixed address alongside the wildcard. That may matter if your network filters which hosts Claude Code can reach.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}