The 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.
Startup onboarding/dialog sequence rewritten to a step-list runner
The startup onboarding sequence was rewritten as a step-list runner, folding in the Chrome policy check.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Terminal UIArea: what it touches
Internal ChangesKind: in v2.1.260,
Internal ChangesSection of the release