{"version":"2.1.307","anchor":"launcher-sign-in-step-in-startup","canonical_anchor":"launcher-sign-in-step-in-startup","heading":"Startup can run a sign-in step for launcher-started sessions","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/launcher-sign-in-step-in-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Startup can run a sign-in step for launcher-started sessions\n\nClaude Code's startup can now run and wait on a sign-in step for sessions started by a launcher\n\n**Unclear.** What triggers this sign-in step and what it does for the person signing in is not known.\n\n**What**\n\nWhen Claude Code starts, it can now run a sign-in step for sessions started by a launcher (another program that starts Claude Code for you). It waits for that step to finish before carrying on. Whether the step runs depends on how the session was started, such as the input format, whether it connects to a remote session, and whether standard input is open.\n\n**Why**\n\nIt is a new startup path that only applies to sessions started this way.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}