Skip to content

Hide banner on first-run before auth#208

Draft
gtsiolis wants to merge 2 commits intomainfrom
des-208-move-header-after-auth-flow-on-first-run
Draft

Hide banner on first-run before auth#208
gtsiolis wants to merge 2 commits intomainfrom
des-208-move-header-after-auth-flow-on-first-run

Conversation

@gtsiolis
Copy link
Copy Markdown
Member

On first interactive run with no auth token, run the device-flow login before launching the start UI so the header doesn't render with (No license) while authentication is still pending. This will hide the banner during the login flow and render the header after login succeeds and the start UI takes over with a resolved license label.

BEFORE AFTER
Screenshot 2026-04-28 at 11 57 10 Screenshot 2026-04-28 at 11 54 38

@carole-lavillonniere
Copy link
Copy Markdown
Collaborator

I would like to rework this because here we spin up two sequential TUI: one for login, then exit, and new TUI for start. That's not following the existing pattern (one TUI per command) and is a bit surprising.

@carole-lavillonniere carole-lavillonniere marked this pull request as draft April 28, 2026 09:41
@carole-lavillonniere carole-lavillonniere force-pushed the des-208-move-header-after-auth-flow-on-first-run branch from 20fb41d to c181cee Compare April 29, 2026 07:17
@carole-lavillonniere carole-lavillonniere force-pushed the des-208-move-header-after-auth-flow-on-first-run branch from c181cee to 4dc7387 Compare April 29, 2026 07:43
Copy link
Copy Markdown
Member Author

@gtsiolis gtsiolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd expect the header to be injected in a linear way after the authentication is complete. Now the header is injected above the welcome message when the authentication completes which reminds me of layout shift in browsers.

Before authentication After authentication
Screenshot 2026-04-29 at 12 41 14 Screenshot 2026-04-29 at 12 41 24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants