{"version":"2.1.265","anchor":"new-fs-filesystem-api-for-plugins-with-readwrite-size-l","canonical_anchor":"new-fs-filesystem-api-for-plugins-with-readwrite-size-l","heading":"New $.fs.* filesystem API for plugins with read\/write size limits","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-fs-filesystem-api-for-plugins-with-readwrite-size-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New $.fs.* filesystem API for plugins with read\/write size limits\n\nPlugins get a new file system API for reading, writing, and listing files, capped at 4MB\n\n**What**\n\nPlugins now have a filesystem API with `readFile`, `writeFile`, `exists`, `stat`, and `listDir` operations, all scoped to a resolved working directory. Both reads and writes are capped at 4,194,304 bytes (4MB); exceeding the limit returns an explicit refusal saying the file is over the byte limit.\n\n**Why**\n\nThis lets plugins interact directly with files on disk in a controlled way, with a size limit that prevents a plugin from reading or writing unexpectedly huge files.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}