{"version":"2.1.267","anchor":"connector-registry-errors-no-longer-double-wrapped","canonical_anchor":"connector-registry-errors-no-longer-double-wrapped","heading":"Connector registry errors no longer double-wrapped","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/connector-registry-errors-no-longer-double-wrapped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Connector registry errors no longer double-wrapped\n\nConnector registry errors are no longer stripped of their original message when re-thrown\n\n**What**\n\nWhen looking up or searching connectors (integrations Claude Code can use, such as external tools registered with it) fails, the error handling now checks whether the error is already the registry's own error type. If it is, that original error is passed through as-is. Previously, it would always be caught and wrapped in a brand-new generic error, which lost the original error's message and type. The classes and logger involved were also renamed internally.\n\n**Why**\n\nThis means that when something goes wrong with connector lookups, the actual underlying error message is preserved instead of being replaced with a generic \"Connector registry is unavailable right now\" message, making the real cause easier to see.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}