{"version":"2.1.319","anchor":"connector-flag-on-file-metadata-and-new-reasons","canonical_anchor":"connector-flag-on-file-metadata-and-new-reasons","heading":"Small additions for connector files, tool access and plugin installs","tier":"internal","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/connector-flag-on-file-metadata-and-new-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Small additions for connector files, tool access and plugin installs\n\nFile details gain a marker for connector files, plus a new reason for refusing a tool result and a new plugin install error label\n\n**Unclear.** How any of these three affect what a reader sees is not shown.\n\n**What**\n\nThree small internal additions appear:\n\n- File details now carry a marker saying whether a file came from a connector (an outside service Claude Code is linked to). If the details cannot be read properly, the file is treated as coming from a connector.\n\n- A new reason a tool result can be refused: the place running the tool has no active permission for it.\n\n- A new internal error label for a plugin copy that gave way to the official install of the same plugin.\n\n**Why**\n\nThey are small hints about how connector files, tool access and plugin installs are handled.\n\n- Area: Connectors\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}