{"version":"2.1.268","anchor":"claude-chrome-paired-device-id-environment-override-for-clau","canonical_anchor":"claude-chrome-paired-device-id-environment-override-for-clau","heading":"CLAUDE_CHROME_PAIRED_DEVICE_ID environment override for Claude in Chrome pairing","tier":"use","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/claude-chrome-paired-device-id-environment-override-for-clau","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### CLAUDE_CHROME_PAIRED_DEVICE_ID environment override for Claude in Chrome pairing\n\nA new CLAUDE_CHROME_PAIRED_DEVICE_ID env var pins which paired browser device Claude in Chrome connects to\n\n**What**\n\nClaude in Chrome (the browser extension bridge that lets Claude Code control a Chrome browser) can now be pointed at a specific paired device using a new `CLAUDE_CHROME_PAIRED_DEVICE_ID` environment variable. When set, this value is checked against the expected device-id format; if it doesn't match, Claude Code ignores it and logs a warning instead of using it.\n\n**Why**\n\nThis lets you pin bridge setup to one specific browser-extension device rather than letting Claude Code pick automatically, which matters if you have more than one paired device and want predictable connections. The format validation means a mistyped or malformed id fails safely with a warning rather than causing a confusing connection error.\n\n- Area: Chrome & Browser\n- Names: `CLAUDE_CHROME_PAIRED_DEVICE_ID`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}