{"version":"2.1.268","anchor":"bug-fix-wrong-exception-object-interpolated-into-connected","canonical_anchor":"bug-fix-wrong-exception-object-interpolated-into-connected","heading":"Bug fix: wrong exception object interpolated into connected-client wiring error","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bug-fix-wrong-exception-object-interpolated-into-connected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bug fix: wrong exception object interpolated into connected-client wiring error\n\nFixed a bug where connected-client wiring errors logged the wrong exception\n\n**What**\n\nIn the code path that adopts a connected MCP client, an error message logged when wiring fails previously referenced an unrelated variable instead of the actual exception that was caught. It now correctly logs the real caught error.\n\n**Why**\n\nThis makes the \"connected-client wiring failed\" log message actually useful for diagnosing what went wrong, since it now shows the real error instead of an unrelated value.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}