{"version":"2.1.310","anchor":"plugin-model-fork-passes-per-plugin-modelcallnames","canonical_anchor":"plugin-model-fork-passes-per-plugin-modelcallnames","heading":"Model calls started by plugins can now carry names","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/plugin-model-fork-passes-per-plugin-modelcallnames","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Model calls started by plugins can now carry names\n\nWhen a plugin starts its own model call, it can now pass along names identifying that call\n\n**What**\n\nPlugins (add-ons that extend Claude Code) can start their own separate model call. That call can now carry a set of names identifying it, alongside where the request came from and which hook started it. A hook is a script that runs automatically at certain points. Claude Code already used these call names elsewhere, so plugin calls now use the same system.\n\n**Why**\n\nModel calls started by plugins can now be identified by name, which likely helps with tracking them or deciding which are allowed.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}