Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.233 Home All releases olderv2.1.232 v2.1.234newer
Claude Code v2.1.233

Frontmatter errors now say what actually happens at load time

You'll notice
Useful2 Signal1
Plugins

Broken frontmatter errors now tell you what will actually happen to that component at load time.

What

When a component's YAML frontmatter fails to parse, the validator tells you the runtime consequence for that specific component type rather than a generic parse error.

Details
  • A project agent does not load at all and is treated as a co-located reference document.
  • A plugin agent loads with its name taken from the filename and every other field dropped.
  • Other component types load with empty metadata.
  • A frontmatter block that parses to null is now accepted as an empty mapping instead of reported as a type error.
Evidence

At runtime this agent loads with its name taken from the filename and every other frontmatter field silently dropped.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.233 →