{"version":"2.1.323","anchor":"startup-non-default-start-path-and-new-migration-step","canonical_anchor":"startup-non-default-start-path-and-new-migration-step","heading":"Changes to how Claude Code starts up","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/startup-non-default-start-path-and-new-migration-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Changes to how Claude Code starts up\n\nStartup gains an optional extra setup step, a step after settings migrations, and a sign-in option for starting a session\n\n**Unclear.** The option that triggers the extra setup step is not identified, so it is unclear whether or how a user can turn it on.\n\n**What**\n\nClaude Code's startup sequence has a few additions:\n\n- One startup option now runs an extra setup step before Claude Code looks for the project's configuration folder.\n\n- When that option is set, Claude Code does not record how long it waited for initialization to finish.\n\n- After stored settings are migrated (converted from an older format to the current one), a check can now run two more steps.\n\n- Sign-in at startup now takes a `startsSession` option, which marks whether that sign-in begins a session (one continuous conversation with Claude Code). It also passes the type of any sign-in error along.\n\n**Why**\n\nThis is a rework of the startup flow. Most people should not notice any difference when Claude Code launches.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}