{"version":"2.1.282","anchor":"plugin-agents-can-now-load-their-definition-on-demand","canonical_anchor":"plugin-agents-can-now-load-their-definition-on-demand","heading":"Plugin agents can load their full definition when they are launched","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/plugin-agents-can-now-load-their-definition-on-demand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Plugin agents can load their full definition when they are launched\n\nA plugin agent can now fetch its definition at launch, and Claude Code shows an error if that definition does not match\n\n**Unclear.** It is unclear whether any plugin agent actually uses this loading path yet, or whether it is switched on.\n\n**What**\n\nAn agent is a helper that Claude Code can hand a task to, and plugins (add-on packages) can supply their own. A plugin agent can now provide a way to load its definition, meaning its instructions and settings, at the moment it is launched instead of using the version listed earlier.\n\nWhen that happens, Claude Code checks that the loaded definition is the same kind of agent and still comes from a plugin. If either check fails, the launch stops with an error saying the agent could not be loaded from its plugin.\n\n**Why**\n\nThis suggests plugin agents may be loaded only when they are needed rather than all at startup. If a plugin agent fails with the new error, the definition it loaded did not match what was expected.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}