{"version":"2.1.251","anchor":"background-terminals-now-also-kill-the-repl-session-behind-t","canonical_anchor":"background-terminals-now-also-kill-the-repl-session-behind-t","heading":"Background terminals now also kill the REPL session behind them","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/background-terminals-now-also-kill-the-repl-session-behind-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Background terminals now also kill the REPL session behind them\n\nKilling a background terminal now also ends the REPL process behind it.\n\n**What**\n\nA background pseudo-terminal now looks up and remembers the session id of the REPL process it belongs to when it first connects, and signals that session too when the terminal is killed or exits, so stray processes are less likely to survive.\n\n**Details**\n\n- The session id is surfaced through an `onRepl` callback on the background-pty client.\n- Skipped on Windows.\n\n**Evidence**\n\n`onRepl`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}