{"version":"2.1.274","anchor":"plugin-agent-loader-refactored-to-take-a-single-options-obje","canonical_anchor":"plugin-agent-loader-refactored-to-take-a-single-options-obje","heading":"Plugin agent loader refactored to take a single options object and drop try\/catch wrapper","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/plugin-agent-loader-refactored-to-take-a-single-options-obje","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Plugin agent loader refactored to take a single options object and drop try\/catch wrapper\n\nThe plugin agent loader now takes a single options object instead of separate arguments, and lost its own error-catching wrapper\n\n**Unclear.** The finding suggests error handling for load failures likely moved to the calling code but doesn't confirm where it now lives.\n\n**What**\n\nThe internal function that builds an agent definition from a plugin's agent markdown file now takes a single destructured options object instead of a list of separate positional arguments. It also no longer has its own try\/catch block that caught load failures, logged an error, and returned null.\n\n**Why**\n\nThis is an internal refactor to how plugin agents are loaded.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}