{"version":"2.1.267","anchor":"relaunchspawn-paths-now-explicitly-uninstall-a-stdout-write","canonical_anchor":"relaunchspawn-paths-now-explicitly-uninstall-a-stdout-write","heading":"Relaunch\/spawn paths now explicitly uninstall a stdout write hook before exec\/kill","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/relaunchspawn-paths-now-explicitly-uninstall-a-stdout-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Relaunch\/spawn paths now explicitly uninstall a stdout write hook before exec\/kill\n\nRelaunch and suspend\/resume paths now explicitly remove a stdout write hook first\n\n**What**\n\nBefore relaunching the CLI as a child process, and before resuming after the process is suspended and continued (`SIGTSTP`\/`SIGCONT`), Claude Code now explicitly calls a helper to uninstall a previously-installed hook that intercepts writes to standard output. Previously these paths either skipped this step or used a different, non-equivalent function.\n\n**Why**\n\nThis avoids leaving the stdout interceptor installed across a relaunch or a suspend\/resume cycle, which could otherwise interfere with output in the new process or after resuming.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}