{"version":"2.1.260","anchor":"startup-onboardingdialog-sequence-rewritten-to-a-step-list","canonical_anchor":"startup-onboardingdialog-sequence-rewritten-to-a-step-list","heading":"Startup onboarding\/dialog sequence rewritten to a step-list runner","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/startup-onboardingdialog-sequence-rewritten-to-a-step-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Startup onboarding\/dialog sequence rewritten to a step-list runner\n\nThe startup onboarding sequence was rewritten as a step-list runner, folding in the Chrome policy check.\n\nThe startup flow covering onboarding, the trust dialog, MCP project approval, CLAUDE.md external includes, the Grove policy dialog, the pro trial screen, powerup discovery, API key approval, Bedrock\/Vertex upgrade offers, dev channels, and Claude-in-Chrome offers has been restructured from sequential inline awaits into an array of step functions run by a shared runner (`na`), with per-step early-outs. This is primarily an internal refactor, but it also folds in the new `allow_claude_browser_extension` check.\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}