Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.257 ·

New hideLoginNotice option splits login-notice display from verbose-token display

The login notice and verbose token display are now computed separately rather than sharing one flag.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTerminal UIwhat it touches
KindInternal Changesin v2.1.257,
Group of 2 Under the hood No documentation found

The login notice and verbose token display are now computed separately rather than sharing one flag.

A 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.

The 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.

Read from
Names in the bundlehideLoginNotice

See this entry in the whole of v2.1.257 →