Default new users to the Agentic UI and remove its feature flag - #4389
Conversation
…to-agentic-ui' into stu-2149-new-users-will-default-to-agentic-ui
📊 Performance Test ResultsComparing 5cc4615 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
…to-agentic-ui' into stu-2149-new-users-will-default-to-agentic-ui
|
@bcotrim Everything works great, I just didn't get this point, coudl you please elaborate?
|
Part of this PR fixes the |
Thanks for the clarification, it works well 👍 |




Related issues
How AI was used in this PR
Claude (Opus 5) implemented the change and ran typecheck + unit tests. New-user and existing-user scenarios verified by hand.
Proposed Changes
falseso a failed migration leaves users where they are.enableAgenticUienv flag, keeping the now-empty registry. CLI Tracks events were labelled from that flag rather than the running UI, so classic users were reported as agentic; fixed.Testing Instructions
Back up
~/.studio/*.json; quit Studio between steps.app.json,cli.json,shared.json→ Agentic UI,ui_version: 'v2'in the log.betaFeatures.enableAgenticUi→ classic, with banner + Settings callout.truewithlastBumpStatspresent → agentic;falsewithlastBumpStatsremoved → classic. Neither should be rewritten.Pre-merge Checklist