{"version":"2.1.224","anchor":"memory-paths-capped-at-1024-bytes-and-reserved-names-refused","canonical_anchor":"memory-paths-capped-at-1024-bytes-and-reserved-names-refused","heading":"Memory paths capped at 1024 bytes and reserved names refused","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/memory-paths-capped-at-1024-bytes-and-reserved-names-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Memory paths capped at 1024 bytes and reserved names refused\n\nMemory paths over 1024 bytes and reserved names like skills or hooks are now refused.\n\n**What**\n\nA memory path longer than 1024 bytes is now rejected, and callers that ask for unsafe segments to be rejected also refuse reserved directory names such as skills, commands, agents and hooks. The refusal message was rewritten and no longer echoes the raw path unescaped.\n\n**Evidence**\n\n`and are not reserved names (skills, commands, agents, hooks, and similar`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}