{"version":"2.1.227","anchor":"markdown-config-files-are-listed-in-one-recursive-pass","canonical_anchor":"markdown-config-files-are-listed-in-one-recursive-pass","heading":"Markdown config files are listed in one recursive pass","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/markdown-config-files-are-listed-in-one-recursive-pass","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Markdown config files are listed in one recursive pass\n\nCommands, agents and output styles load in one recursive listing when the newer storage client is available.\n\n**What**\n\nLoading markdown-backed config from the user config directory (commands, agents, output styles, routines and so on) now makes a single recursive listing request filtered to `.md` files instead of walking directories page by page. This only happens when the newer storage client is available; otherwise the old direct filesystem scan runs unchanged.\n\n**Details**\n\n- On a listing error it logs a warning and falls back to the raw filesystem scan; if the 10000 page cap is hit it keeps the entries already seen and warns.\n- Each file is then read with a bounded read and skipped when its reported total size exceeds 1 MiB, rather than trusting a size from the directory listing.\n- The recursive listing call does not exist at all in v2.1.226.\n\n**Evidence**\n\n`loadMarkdownFilesFromDir: skipping `\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}