{"version":"2.1.257","anchor":"token-usage-warning-notice-now-split-into-login-notice-and-v","canonical_anchor":"new-hideloginnotice-session-option","heading":"New hideLoginNotice option splits login-notice display from verbose-token display","tier":"use","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/token-usage-warning-notice-now-split-into-login-notice-and-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New hideLoginNotice option splits login-notice display from verbose-token display\n\nThe login notice and verbose token display are now computed separately rather than sharing one flag.\n\nA new `hideLoginNotice` flag is threaded through session\/turn controller construction (`Ere`), alongside `debug`, `embedded`, and `hasSuppressedDialogs`, and passed into the status UI component `wD` via a `hideLoginNotice` prop. This lets an embedded\/host session suppress the login-notice chrome separately from the existing `hideWelcomeChrome` flag.\n\nThe status-line component now separately computes `showLoginNotice` (shown when the API key is invalid or missing, unless hidden) and `showVerboseTokens` (shown when the verbose flag is set and the key is valid), passed to the child instead of a single combined flag, giving finer control over when each is displayed.\n\n- Area: Terminal UI\n- Names: `hideLoginNotice`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}