Design errors now explain that logging in once interactively lets headless and SDK runs reuse it.
What's wrong with this entry?
Design errors now tell you that running /design login once from an interactive session on the same machine lets headless and SDK runs reuse that authorization, instead of only reporting that the command is unavailable.
- Applies to both the design sync path and the Claude Design tool.
- The interactive-session message no longer offers logging in with a Claude subscription as an alternative.
non-interactive runs here then reuse that authorization
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.248
Claude Design explains a rejected credential
Both mention design login
-
v2.1.248
Design authorization errors point at /design-login
Both mention design login
-
v2.1.235
Claude Design state moved off module globals onto a per-session object
Both mention design