{"version":"2.1.318","anchor":"startup-mcppermission-tweaks-and-json-schema-etc-unchang","canonical_anchor":"startup-mcppermission-tweaks-and-json-schema-etc-unchang","heading":"Onboarding can relaunch Claude Code after a code-mode opt-in step","tier":"internal","area":"Code Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/startup-mcppermission-tweaks-and-json-schema-etc-unchang","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Onboarding can relaunch Claude Code after a code-mode opt-in step\n\nAfter first-run setup, a code-mode opt-in step can restart Claude Code, and MCP setup now records how long loading took\n\n**Unclear.** What code mode is and when the opt-in step appears are not known.\n\n**What**\n\nTwo startup changes:\n\n- Code-mode opt-in: after the interactive onboarding you go through on first run, a step asking you to opt in to code mode can restart Claude Code on its own.\n\n- MCP timing: Claude Code now measures how long it waits for and loads its MCP configuration. MCP (Model Context Protocol) servers are add-ons that give Claude extra tools.\n\n**Why**\n\nIf Claude Code closes and reopens itself right after setup, that is this new opt-in step and not a crash.\n\n- Area: Code Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}