After signing in, /login holds if your organization's managed settings still need review.
What's wrong with this entry?
After signing in, if your organization's managed settings still need review, /login prints a notice instead of the usual success messages and holds there until you review them.
- The login completion path takes a callback fired when consent is needed; the normal login result messages are suppressed in favour of the notice.
Signed in. Review your organization's managed settings to continue.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.222
MCP server panel explains a rejected claude.ai session token
Both mention login
-
v2.1.222
MCP: rejected claude.ai session token is now visible
Both mention login
-
v2.1.222
Dedicated error when claude.ai rejects a session bearer token
Both mention login