{"version":"2.1.296","anchor":"warning-for-unrecognized-agent-frontmatter-keys-with-did-yo","canonical_anchor":"warning-for-unrecognized-agent-frontmatter-keys-with-did-yo","heading":"Plugin agents now warn about misspelled and unsupported settings","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/warning-for-unrecognized-agent-frontmatter-keys-with-did-yo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Plugin agents now warn about misspelled and unsupported settings\n\nPlugin agent files now log a warning for settings Claude Code does not recognize, suggest the likely intended name, and flag more ignored ones\n\n**What**\n\nAn agent file defines a custom agent, and its frontmatter is the block of settings at the top of the file. When Claude Code loads an agent file that comes from a plugin (an add-on that extends Claude Code), it now logs a warning for any frontmatter setting it does not recognize, and suggests the closest valid name. For example:\n\n- `allowedtools` points to `tools`\n\n- `whentouse` points to `description`\n\nPlugin agents already warned that `permissionMode`, `hooks` and `mcpServers` are ignored for them. They now also warn that these are ignored:\n\n- `initialPrompt`\n\n- `observer`\n\n- `observerMessage`\n\n- `observeSubagents`\n\nThe warning suggests defining the agent in `.claude\/agents\/` to use such a setting.\n\n**Why**\n\nBefore, a misspelled setting in agent frontmatter was dropped without any message, so an agent could quietly run without the setting its author meant to give it. The warning now shows where the mistake is.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}