Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.304 ·

A managed-folder hold withholds organization-managed skills and agents

Organization-managed skills and agents in the managed .claude folder are filtered out while a managed-folder hold is active

Group of 2 You'll notice Improvements
JSON All of v2.1.304
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release

Unclear What turns the managed-folder hold on is not stated.

What

Organizations can supply skills (reusable instructions) and agents (helpers Claude can hand work to) through a managed .claude folder, with the source policySettings. A new hold can keep them out:

  • Skills and agents: the headless command loader filters out prompt skills and agents with source policySettings that live under the managed .claude folder. It does this when a managed-folder hold (managedFolderHold) is active, or when the hold state can't be read and the setting's readAs flag is not false.
  • Agents: new logic (readHold, shedHeldManagedAgents, noteHoldMove) drops such agents when a held: state is read, and rereads agents when the hold moves.
  • Reloads: the loader re-checks when the hold changes, and load errors now trigger a reload. Before, it only reacted to skillOverrides and bundledSkillsDisabled.

Why

Skills and agents your organization manages may be missing for a while when a hold is in place, and come back when it changes.

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 turns the managed-folder hold on is not stated.

See this entry in the whole of v2.1.304 →

Feedback