{"version":"2.1.280","anchor":"two-stub-functions-unconditionally-return-false-right-next","canonical_anchor":"two-stub-functions-unconditionally-return-false-right-next","heading":"Two stub functions unconditionally return false, right next to real session-gating logic","tier":"internal","area":"CLI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/two-stub-functions-unconditionally-return-false-right-next","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Two stub functions unconditionally return false, right next to real session-gating logic\n\nTwo new always-false stub functions appeared next to Claude Code's session-detection logic, purpose unclear\n\n**Unclear.** It's unclear what these two functions do or control, since no caller could be traced in this part of the code.\n\n**What**\n\nThe part of Claude Code that starts up the command-line tool now includes two small new functions that always return `false`, sitting right beside the existing logic that detects things like whether a session is non-interactive or running in remote mode. Because their names overlap with other heavily-reused shorthand names elsewhere in the code, it wasn't possible to trace where or whether anything actually calls them yet.\n\n**Why**\n\nWith no confirmed caller, it's not clear what behavior these functions are meant to gate or disable. They may be early scaffolding for a future check that isn't wired up yet.\n\n- Area: CLI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}