{"version":"2.1.274","anchor":"plugin-agents-can-now-load-from-a-hooks-module-files-map","canonical_anchor":"plugin-agents-can-now-load-from-a-hooks-module-files-map","heading":"Plugin agents can now load from a hooks-module 'files' map, not just a folder","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/plugin-agents-can-now-load-from-a-hooks-module-files-map","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Plugin agents can now load from a hooks-module 'files' map, not just a folder\n\nPlugin agents can now load hooks from a files map, not just a folder\n\n**What**\n\nPlugins that define agents can now supply their hooks module (code that runs around tool or agent actions) in two ways: the existing folder-based layout, or a new files-object keyed by namespace paths. In the new form, each entry is turned into a synthetic `builtin:` file path and parsed individually.\n\n**Why**\n\nThis gives plugin authors a second, more flexible way to package hooks without needing a folder structure on disk.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}