"design" removed as a standalone CLI action while…

Under the hood

Plain "design" CLI action removed while design-consent, design-revoke and design-login remain

What

The internal list of CLI command categories no longer includes a standalone design entry. The related design-consent, design-revoke, and design-login actions are still present and unaffected.

Why

The finding does not explain what the plain design action did or why it was dropped, only that it is no longer in the category map while its related subcommands remain.

How sure we are

Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.

The writer flagged doubtWhat the standalone "design" action did, and whether it was actually reachable as a command, is not stated.

Anthropic's release notes agreeFixed /login showing "no gateway URL is configured" when re-run in a session that signed in to a Claude apps gateway set by managed settings

See this entry in the whole of v2.1.265 →

The build it came inv2.1.265

8 Sep 2026 · 371 entries, this one is #312.

Use it now40
You'll notice132
Nothing to try yet30
Under the hood169

Open the release →

Anthropic's note

Upstream's own release notes for v2.1.265 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed /login showing "no gateway URL is configured" when re-run in a session that signed in to a Claude apps gateway set by managed settings

Either side of it

v2.1.263Older
v2.1.266Newer

Is this right?

"design" removed as a standalone CLI action while design-consent/revoke/login remain