{"version":"2.1.242","anchor":"chrome-connector-repairs-its-own-launcher-permissions","canonical_anchor":"chrome-connector-repairs-its-own-launcher-permissions","heading":"Chrome connector repairs its own launcher permissions","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/chrome-connector-repairs-its-own-launcher-permissions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Chrome connector repairs its own launcher permissions\n\nThe Chrome launcher script is quoted properly and gets its executable permission repaired.\n\n**What**\n\nThe small script Chrome uses to launch Claude is now written from a proper argument list, quoted for the platform (`%` doubled on Windows), and when the script already exists with the right contents its executable permission is reset to 0755 instead of being left broken.\n\n**Details**\n\n- If the permission repair fails, it logs \"[Claude in Chrome] Could not repair wrapper exec bit\" rather than silently handing back a script that will not run.\n\n**Evidence**\n\n`[Claude in Chrome] Could not repair wrapper exec bit: `\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}