{"version":"2.1.302","anchor":"background-session-controlling-terminal-acquisition-now-uses","canonical_anchor":"background-session-controlling-terminal-acquisition-now-uses","heading":"Background sessions get their terminal through a different method","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/background-session-controlling-terminal-acquisition-now-uses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Background sessions get their terminal through a different method\n\nBackground sessions now claim a controlling terminal through a function built into Claude Code's runtime instead of a separate system lookup\n\n**What**\n\nA background session is a Claude Code session that keeps running without a terminal window open in front of you. To work properly it needs a controlling terminal, which is the terminal a program belongs to and takes keyboard input and signals from. Claude Code used to find the system function that does this through a separate lookup. It now calls a function built into the runtime it ships with.\n\nIf that call cannot be made at all, Claude Code logs a message and reports the method as unavailable. If the call runs but does not succeed, it is still reported as failed.\n\n**Why**\n\nBackground sessions that used to stop because the old lookup was not available may now get a terminal.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}