Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.293 ·

Monitor watches report why they closed, plus a fixed MCP app sandbox host

Monitor watches now emit a close event saying why they stopped, and a fixed MCP app sandbox host was added

Group of 2 Under the hood Internal Changes
JSON All of v2.1.293
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.293,
Internal ChangesSection of the release

What

A 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.

In 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.

Why

The 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.

See this entry in the whole of v2.1.293 →

Feedback