What
/auto-mode-setup drafts auto mode settings by scanning your project and recent sessions. Before that scan, it now checks that you are signed in. If the check fails, setup stops and tells you to run /login and then run /auto-mode-setup again. It reports whether the login has expired or you are not signed in at all.
The check passes when an API key or an apiKeyHelper is set up.
Why
If your login has expired, you now get a clear instruction instead of a scan that fails for no obvious reason.
Names in the bundle/auto-mode-setup/login
Documented inclaude-code/auto-mode-config
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether the login check applies in every environment, since part of the condition that triggers it was not identified.
Anthropic's release notes agree
Improved the startup refusal when managed settings require a sign-in (forceLoginMethod or forceLoginOrgUUID) and an API key, token or…