{"version":"2.1.267","anchor":"nonblocking-stdout-install-failures-get-richer-deduplicated","canonical_anchor":"nonblocking-stdout-install-failures-get-richer-deduplicated","heading":"Nonblocking stdout install failures get richer, deduplicated telemetry","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/nonblocking-stdout-install-failures-get-richer-deduplicated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Nonblocking stdout install failures get richer, deduplicated telemetry\n\nFailures installing the fast, non-blocking stdout writer now log more detail and report telemetry once per reason\n\n**Unclear.** The finding does not say what effect, if any, this has on the reader beyond diagnostics; behavior when the fast path fails to install is otherwise unspecified.\n\n**What**\n\nClaude Code uses a fast, non-blocking way of writing to the terminal's standard output when possible. When that setup fails to install, the log message now includes the specific system error code (errno) instead of a generic message. A new 'skipped' telemetry event is also sent, but only once per distinct failure reason (duplicates are filtered out), alongside the existing 'installed' event that already reported successes.\n\n**Why**\n\nThis makes it easier to diagnose why the faster output path isn't being used on a given system, without flooding telemetry with repeated identical failure reports.\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}