{"version":"2.1.227","anchor":"renderer-survives-a-dead-stdout-under-the-daemon-background-","canonical_anchor":"renderer-survives-a-dead-stdout-under-the-daemon-background-","heading":"Renderer survives a dead stdout under the daemon background backend","tier":"use","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/renderer-survives-a-dead-stdout-under-the-daemon-background-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Renderer survives a dead stdout under the daemon background backend\n\nWith the daemon background backend, the display survives stdout disappearing instead of dying.\n\n**What**\n\nSetting `CLAUDE_BG_BACKEND=daemon` now makes the terminal renderer tolerate stdout going away instead of treating it as fatal.\n\n**Details**\n\n- The terminal wrapper tracks whether tolerance is on and whether stdout has already died.\n- Separately, the warnings about garbage or absurd terminal dimensions moved from a once-per-process flag to a per-renderer callback, so a second renderer can still warn.\n\n**Evidence**\n\n`tolerateDeadStdout: re.CLAUDE_BG_BACKEND === \"daemon\"`\n\n- Area: Background Tasks\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}