Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.277entry #98

Claude Code v2.1.277 ·

New reserved-name lock for skills, commands and tools

Skills, commands and tools whose name collides with a reserved settings key now get a distinct 'reserved-name' lock

Group of 4 You'll notice Internal Changes
JSON All of v2.1.277
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.277,
ImprovementsSection of the release

Unclear The finding doesn't say what triggers the 'reserved-name' origin or which skill/tool names are reserved.

What

  • Skills whose name fails a new reserved-name check are locked to on/user-invocable-only, ignoring any user override.
  • The permissions UI now shows a distinct "reserved-name" state when a skill's or command's configured name can't be stored in settings because it collides with a reserved key, with guidance to rename the skill's folder or the command file.
  • Tools or commands named exactly __proto__ are always treated as reserved-name and forced to stay callable (on or user-invocable-only), regardless of user or policy settings for slash-command visibility.
  • The permission-mode cycling control now treats "reserved-name" the same as "policy" or "flag" sources: it leaves the mode unchanged instead of letting it be cycled.

Why

Names like __proto__ can collide with reserved keys used internally by settings storage, which previously could cause confusing or unsafe override behavior. The new reserved-name category makes this collision visible in the UI and stops such names from being silently disabled, hidden, or mis-cycled.

Read from
Names in the bundlereserved-name
What the documentation says
Documented inclaude-code/errors
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Marketplace reference touched a line naming reserved-name after this was published. | `name` | string | Marketplace identifier: letters, digits, `.`, `_`, and `-`, starting with a letter or digit, and no `..`. `claude plugin validate` fails any other name, because Claude Code can't install plugins from a marketplace that … plugins/marketplace-reference see the edit
Confirmed since Anthropic's documentation has since written up reserved-name, on Error reference. | `"<name>" is another spelling of "<reserved>", a reserved marketplace name` | [Plugin errors](#marketplace-name-is-another-spelling-of-a-reserved-name) | errors see the edit
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 doubtThe finding doesn't say what triggers the 'reserved-name' origin or which skill/tool names are reserved.
Anthropic's documentation agreesAnthropic's documentation has since written up reserved-name, on Error reference.

See this entry in the whole of v2.1.277 →

Feedback