{"version":"2.1.209","anchor":"background-sessions-now-support-login-and-model","canonical_anchor":"background-sessions-now-support-login-and-model","heading":"Background Sessions Now Support \/login and \/model","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.209\/e\/background-sessions-now-support-login-and-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.209","markdown":"### Background Sessions Now Support \/login and \/model\n\nBackground sessions (headless\/remote jobs) previously blocked both the `\/login` command and the `\/model` model picker with hard errors. Those restrictions have been removed \u2014 both commands now work the same way in background sessions as in interactive terminals.\n\nThe following messages were removed from the codebase:\n\n- \"Can't run \/login in a background session \u2014 log in from a regular interactive terminal (`claude`), then respawn this job.\"\n- \"Can't open the model picker in a background session \u2014 use `\/model <name>` to switch this session's model.\"\n\nThe model fable consent flow (for usage-credits consent when switching to certain models) also no longer short-circuits in background sessions.\n\n**Evidence**\n\n`si()` (is-background-session) guard removed from the `\/login` handler (search for `\"Can't run \/login in a background session\"`); same guard removed from the model picker and model-switch flow (search for `\"Can't open the model picker in a background session\"`)"}