Chrome extension not connecting on Windows

I have also been having the same issue. it is also on windows. i was using the cc cli within antigravity.

Guys, I fixed it:

Bug Report: Claude-in-Chrome broken on Windows

Component: Claude Code CLI — built-in claude-in-chrome MCP server
Platform: Windows (all versions)
Severity: All Claude-in-Chrome browser tools are non-functional on Windows
Affects: Claude Code v2.1.x (standalone .exe — confirmed on v2.1.32)

---

Summary

Every mcp__claude-in-chrome__* tool call on Windows returns:

"Browser extension is not connected. Please ensure the Claude browser extension is installed and running..."

This happens even when the Chrome extension is installed, enabled, and the
native messaging host is running correctly. The Chrome extension, native host,
and named pipe all work — Claude Code just never connects to the pipe.

---

Root cause

The getSocketPaths() function (minified as xYI() in v2.1.32) returns
Unix-style socket paths on all platforms, including Windows. It never returns
the Windows named pipe path.

Broken function (xYI):

function xYI() {
  let H = [], $ = NkH();                          // NkH() = "/tmp/claude-mcp-browser-bridge-{user}"
  try {
    let I = YYI.readdirSync($);                    // readdir("/tmp/...") — always fails on Windows
    for (let f of I)
      if (f.endsWith(".sock")) H.push(uY.join($, f));
  } catch {}
  let A = `claude-mcp-browser-bridge-${CzA()}`;
  let L = uY.join(cy.tmpdir(), A);                // e.g. "C:\Users\...\AppData\Local\Temp\claude-mcp-browser-bridge-user"
  let D = `/tmp/${A}`;                             // Unix path — doesn't exist on Windows
  if (!H.includes(L)) H.push(L);
  if (L !== D && !H.includes(D)) H.push(D);
  return H;                                        // Returns temp-dir paths, NEVER the named pipe
}

On Windows, this returns paths like:

["C:\\Users\\user\\AppData\\Local\\Temp\\claude-mcp-browser-bridge-user",
 "/tmp/claude-mcp-browser-bridge-user"]

Neither of these is the actual named pipe.

Working companion function (rN$):

The getSocketPath() function (minified as rN$()) already has the correct
Windows logic:

function rN$() {
  if (cy.platform() === "win32")
    return `\\\\.\\pipe\\${p1E()}`;                // \\.\pipe\claude-mcp-browser-bridge-{user}
  return uY.join(NkH(), `${process.pid}.sock`);
}

This function correctly returns \\.\pipe\claude-mcp-browser-bridge-{user} on
Windows, but getSocketPaths() never calls it.

How the socket pool uses these functions:

// In the MCP server setup (DoI):
let config = {
  socketPath: rN$(),           // Correct — used for creating a server socket
  getSocketPaths: xYI,         // Broken — used for discovering existing sockets
};

// In the socket pool (viI):
getAvailableSocketPaths() {
  return this.context.getSocketPaths?.() ?? [];    // Calls xYI() — gets wrong paths
}

refreshClients() {
  let paths = this.getAvailableSocketPaths();      // Wrong paths on Windows
  for (let path of paths)
    if (!this.clients.has(path))
      // Creates socket client for wrong path — connection fails silently
}

The socket pool discovers paths via getSocketPaths() (broken), creates
clients for those wrong paths, they all fail to connect, and the pool reports
zero connected clients → "Browser extension is not connected."

---

The fix

Add a Windows early-return to getSocketPaths():

function getSocketPaths() {
  if (os.platform() === "win32") return [getSocketPath()];
  // ... existing Unix logic unchanged ...
}

This is a one-line change. The getSocketPath() function already does the
right thing on Windows.

Important: two copies in the binary

The standalone .exe bundles two copies of this function (at different
offsets in the bundled JS). Both must be fixed. In v2.1.32 they are at byte
offsets 0x75729DB and 0xCBDBCCB.

---

How to reproduce

1. Install Claude Code on Windows (standalone .exe)
2. Install the "Claude in Chrome" extension in Chrome
3. Log into claude.ai in Chrome
4. Open a terminal, run claude
5. Ask Claude to use any browser tool (e.g. "take a screenshot of google.com")
6. Observe: "Browser extension is not connected"

Verification that the pipe works:

While Chrome is open with the extension active, run this Node.js script:

const net = require('net');
const os = require('os');
const pipe = `\\\\.\\pipe\\claude-mcp-browser-bridge-${os.userInfo().username}`;

const c = net.connect(pipe);
c.on('connect', () => { console.log('CONNECTED'); c.end(); });
c.on('error', (e) => { console.log('Error:', e.message); });

This will print CONNECTED — proving the Chrome extension's native host is
running and the pipe is alive. Claude Code just never tries to connect to it.

Full protocol test:

const net = require('net');
const os = require('os');
const pipe = `\\\\.\\pipe\\claude-mcp-browser-bridge-${os.userInfo().username}`;

const c = net.connect(pipe);
c.on('connect', () => {
  const msg = JSON.stringify({
    method: "execute_tool",
    params: { client_id: "claude-code", tool: "tabs_context_mcp", args: { createIfEmpty: true } }
  });
  const msgBuf = Buffer.from(msg, 'utf-8');
  const lenBuf = Buffer.allocUnsafe(4);
  lenBuf.writeUInt32LE(msgBuf.length, 0);
  c.write(Buffer.concat([lenBuf, msgBuf]));
});

c.on('data', (data) => {
  if (data.length >= 4) {
    const len = data.readUInt32LE(0);
    if (data.length >= 4 + len)
      console.log('Response:', data.slice(4, 4 + len).toString('utf-8'));
  }
  c.end();
});

This returns actual tab data — the entire pipeline works except for the path
discovery in Claude Code itself.

---

Architecture diagram

Chrome Extension
    │
    │ chrome.runtime.connectNative("com.anthropic.claude_code_browser_extension")
    ▼
chrome-native-host.bat → claude.exe --chrome-native-host
    │
    │ Creates named pipe: \\.\pipe\claude-mcp-browser-bridge-{user}
    │ Listens for connections
    ▼
Named Pipe (Windows) ◄──── Claude Code tries to connect here
    │                       BUT getSocketPaths() returns wrong paths
    │                       so it never finds this pipe
    ▼
Claude Code MCP Server
    │
    │ Returns: "Browser extension is not connected"
    ▼
User sees error

---

Related issues

• #21371 — Not connecting despite being installed
• #23218 — Not connecting on Windows 11
• #21300 — Not connecting despite MCP showing connected
• #21363 — Native messaging on Windows 11
• #21301 — MCP connection fails on Windows
• #22500 — MCP shows connected but extension unresponsive

All of these are the same root cause.

---

Confirmed working after patch

After applying a binary patch that adds the Windows early-return to both copies
of getSocketPaths(), all browser tools work correctly:

• tabs_context_mcp — returns tab list
• navigate — navigates to URLs
• computer (screenshot) — captures screenshots
• read_page — reads accessibility tree
• find — finds elements
• javascript_tool — executes JS in page context

The fix has been tested and confirmed working on Windows 11 with Claude Code
v2.1.32 (standalone exe).

Give this to Opus 4.6:

Fix: Claude-in-Chrome Not Connecting on Windows

The "Claude in Chrome" browser automation tools don't work on Windows. Every call
returns "Browser extension is not connected" even though the extension is
installed, enabled, and you're logged in.

This is a known bug in Claude Code on Windows (as of February 2026).
The fix below patches the binary so the tools work correctly.

---

Who is this for?

You need this fix if all three of these are true:

1. You're on Windows
2. You have the Claude in Chrome extension installed in Chrome
3. Every browser tool returns "Browser extension is not connected"

What's the bug?

Claude Code discovers browser connections through socket paths. On Windows, it
should look for a named pipe (\\.\pipe\claude-mcp-browser-bridge-{user}),
but the discovery function returns Unix-style paths (/tmp/...) instead.
The pipe exists and works fine - Claude Code just never looks in the right place.

Prerequisites

• Node.js installed (you already have this if Claude Code works)
• Claude Code installed (standalone .exe version)

---

Step-by-step instructions

Step 1: Find your claude.exe

Open a terminal (Command Prompt, PowerShell, or Git Bash) and run:

where claude

This will print something like:

C:\Users\YourName\.local\bin\claude.exe

Copy that path. You'll need it in Step 3.

Step 2: Save the patch script

Create a file called patch-claude-chrome.js anywhere on your computer
(e.g. your Desktop). Paste this entire script into it:

#!/usr/bin/env node
/**
 * Binary patch for Claude Code to fix Claude-in-Chrome on Windows.
 *
 * Bug:  getSocketPaths() returns Unix paths on Windows, missing the named pipe.
 * Fix:  Adds early return for win32 that returns the correct named pipe path.
 *
 * Safe: creates a .patched file instead of overwriting the original.
 *       Also creates a .backup copy before the first patch.
 *
 * IMPORTANT: The binary contains TWO copies of the broken function.
 *            This script patches ALL of them.
 *
 * Usage:  node patch-claude-chrome.js [path-to-claude.exe]
 *
 * If no path is given, it tries the default install location.
 */

const fs = require("fs");
const path = require("path");
const crypto = require("crypto");
const os = require("os");

// --- Resolve claude.exe path ---
const defaultPath = path.join(os.homedir(), ".local", "bin", "claude.exe");
const target = process.argv[2] || defaultPath;

if (!fs.existsSync(target)) {
  console.error(`ERROR: File not found: ${target}`);
  console.error(`\nUsage: node patch-claude-chrome.js "C:\\path\\to\\claude.exe"`);
  process.exit(1);
}

// --- Patch definitions (must be exactly the same byte length) ---

const ORIGINAL =
  'function xYI(){let H=[],$=NkH();try{let I=YYI.readdirSync($);for(let f of I)' +
  'if(f.endsWith(".sock"))H.push(uY.join($,f))}catch{}let A=`claude-mcp-browser-' +
  'bridge-${CzA()}`,L=uY.join(cy.tmpdir(),A),D=`/tmp/${A}`;if(!H.includes(L))H.' +
  'push(L);if(L!==D&&!H.includes(D))H.push(D);return H}';

const PATCHED =
  'function xYI(){if(cy.platform()==="win32")return[rN$()];let H=[],$=NkH();try{' +
  'let I=YYI.readdirSync($);for(let f of I)if(f.endsWith(".sock"))H.push(uY.join' +
  '($,f))}catch{}let A=`claude-mcp-browser-bridge-${CzA()}`,L=uY.join(cy.tmpdir(' +
  '),A);if(!H.includes(L))H.push(L);return H /*W32*/}';

if (Buffer.byteLength(ORIGINAL) !== Buffer.byteLength(PATCHED)) {
  console.error("FATAL: patch length mismatch (this is a script bug).");
  process.exit(1);
}

// --- Read binary ---

console.log(`\nReading: ${target}`);
const bin = fs.readFileSync(target);
console.log(`Size: ${(bin.length / 1024 / 1024).toFixed(1)} MB`);

const hashBefore = crypto.createHash("sha256").update(bin).digest("hex").slice(0, 16);
console.log(`SHA-256: ${hashBefore}...`);

// --- Find and patch ALL occurrences ---

const origBuf = Buffer.from(ORIGINAL);
const patchBuf = Buffer.from(PATCHED);

let patchCount = 0;
let offset = 0;
while (true) {
  const idx = bin.indexOf(origBuf, offset);
  if (idx === -1) break;
  console.log(`Found unpatched copy at offset ${idx} (0x${idx.toString(16)})`);
  patchBuf.copy(bin, idx);
  offset = idx + origBuf.length;
  patchCount++;
}

// Count already-patched copies
let alreadyPatched = 0;
offset = 0;
while (true) {
  const idx = bin.indexOf(patchBuf, offset);
  if (idx === -1) break;
  alreadyPatched++;
  offset = idx + patchBuf.length;
}

console.log(`\nNewly patched: ${patchCount}`);
console.log(`Already patched: ${alreadyPatched - patchCount}`);
console.log(`Total patched copies: ${alreadyPatched}`);

if (patchCount === 0 && alreadyPatched > 0) {
  console.log("\n  Already fully patched! Nothing to do.");
  console.log("  If it's still not working, make sure you restarted Claude Code.\n");
  process.exit(0);
}

if (patchCount === 0 && alreadyPatched === 0) {
  console.error("\nERROR: Could not find the target function in this binary.");
  console.error("This patch was written for a specific version of Claude Code.");
  console.error("Your version may already include a fix, or the function was renamed.\n");
  process.exit(1);
}

// --- Create backup (only if one doesn't exist) ---

const backupPath = target + ".backup";
if (!fs.existsSync(backupPath)) {
  fs.copyFileSync(target, backupPath);
  console.log(`Backup saved: ${backupPath}`);
} else {
  console.log(`Backup already exists: ${backupPath}`);
}

// --- Write patched binary ---

const patchedPath = target + ".patched";
fs.writeFileSync(patchedPath, bin);

const hashAfter = crypto.createHash("sha256").update(bin).digest("hex").slice(0, 16);
console.log(`Patched SHA-256: ${hashAfter}...`);
console.log(`\nPatched file written to: ${patchedPath}`);

// --- Print next steps ---

console.log(`
=======================================
  PATCH CREATED SUCCESSFULLY
=======================================

Now do these steps IN ORDER:

  1. CLOSE all Claude Code terminal sessions
     (type /exit in each one, or close the terminals)

  2. Replace the original with the patched file.
     Open a NEW terminal and run one of these:

     Command Prompt:
       copy /Y "${patchedPath}" "${target}"

     PowerShell:
       Copy-Item -Path "${patchedPath}" -Destination "${target}" -Force

  3. RESTART Chrome (close all Chrome windows, reopen)

  4. Open a new terminal and run: claude

  5. Test with any browser tool, e.g. ask Claude to
     "take a screenshot of google.com"

If you need to undo the patch later:

     Command Prompt:
       copy /Y "${backupPath}" "${target}"

     PowerShell:
       Copy-Item -Path "${backupPath}" -Destination "${target}" -Force
`);

Step 3: Run the patch script

Open a terminal and run:

node patch-claude-chrome.js

If your claude.exe is not in the default location (~/.local/bin/claude.exe),
pass the path from Step 1:

node patch-claude-chrome.js "C:\Users\YourName\.local\bin\claude.exe"

You should see output ending with "PATCH CREATED SUCCESSFULLY" and it
should report patching 2 copies of the function.

Step 4: Close all Claude Code sessions

Type /exit in every open Claude Code session, or just close the terminal
windows. Claude Code must not be running for the next step to work.

Step 5: Replace the original binary

Open a new terminal and run the appropriate command for your shell:

Command Prompt:

copy /Y "%USERPROFILE%\.local\bin\claude.exe.patched" "%USERPROFILE%\.local\bin\claude.exe"

PowerShell:

Copy-Item -Path "$env:USERPROFILE\.local\bin\claude.exe.patched" -Destination "$env:USERPROFILE\.local\bin\claude.exe" -Force

If your path is different, adjust accordingly. You should see 1 file(s) copied
(Command Prompt) or no error (PowerShell).

If you get "being used by another process": Make sure you closed ALL Claude
Code sessions in Step 4. Check Task Manager for any remaining claude.exe
processes and end them.

Step 6: Restart Chrome

Close all Chrome windows completely, then reopen Chrome. Visit any webpage
to activate the extension.

Step 7: Start Claude Code and test

Open a new terminal, run claude, and try any browser tool. For example:

Take a screenshot of google.com

If Claude returns tab information or a screenshot, the fix is working!

---

Troubleshooting

"Could not find the target function in this binary"

The patch was written for a specific Claude Code version. If you're on a newer
version, the function may have been renamed or already fixed. Check GitHub
issues for updates.

"being used by another process" when copying

Claude Code is still running. Close ALL terminal windows running Claude Code.
If it still fails, open Task Manager (Ctrl+Shift+Esc), find claude.exe in
the processes list, and click "End Task" on each one. Then try the copy again.

It says "patched 1 copy" but still doesn't work

The binary contains 2 copies of the broken function. If only 1 was patched,
run the script again - it will find and patch the remaining copy. Make sure
you do the full copy + restart cycle again after.

The fix stopped working after an update

Claude Code auto-updates will overwrite the patched binary. Just re-run the
patch script (Steps 3-7) after each update, until Anthropic ships an official
fix.

How to undo the patch

Command Prompt:

copy /Y "%USERPROFILE%\.local\bin\claude.exe.backup" "%USERPROFILE%\.local\bin\claude.exe"

PowerShell:

Copy-Item -Path "$env:USERPROFILE\.local\bin\claude.exe.backup" -Destination "$env:USERPROFILE\.local\bin\claude.exe" -Force

---

@ivanjuras I tried on 2.1.37 and 2.1.32, it doesn't help. I noticed that the chrome extension updated a couple days ago, which is when it seemed to stop working for me. I'm trying to find an older version of that extension but not haveing much luck right now.

It didn't work for me either. I'm going crazy now that Claude Code can't check its work in Chrome anymore after I had relied on that for weeks!

<img width="993" height="1137" alt="Image" src="https://github.com/user-attachments/assets/5bd047e2-6693-4a00-8847-472162ac03c0" />

WELL, I asked claude.ai to update that patch for the current version of Claude Code, and it worked! Run the following as a .js file in a fresh terminal, and then follow the instructions that it prints into the terminal:

#!/usr/bin/env node
/**

• Binary patch for Claude Code v2.1.37 to fix Claude-in-Chrome on Windows.

*

• Bug: ZKI() (getSocketPaths) only returns Unix socket paths on Windows,
• missing the Windows named pipe path that the native host listens on.
• Fix: Adds early return for win32 that returns \\\\.\\pipe\\claude-mcp-browser-bridge-{user}

*

• Creates a .patched file (does not overwrite original).
• Also creates a .backup on first run.

*

• Usage: node patch-claude-chrome-v2.js [path-to-claude.exe]

*/

const fs = require("fs");
const path = require("path");
const crypto = require("crypto");
const os = require("os");

const defaultPath = path.join(os.homedir(), ".local", "bin", "claude.exe");
const target = process.argv[2] || defaultPath;

if (!fs.existsSync(target)) {
console.error("ERROR: File not found: " + target);
console.error("\nUsage: node patch-claude-chrome-v2.js \"C:\\path\\to\\claude.exe\"");
process.exit(1);
}

// Decode patch strings from base64 to avoid escaping hell
const origBuf = Buffer.from("ZnVuY3Rpb24gWktJKCl7bGV0IEg9W10sJD1aa0goKTt0cnl7bGV0IEk9UEtJLnJlYWRkaXJTeW5jKCQpO2ZvcihsZXQgZiBvZiBJKWlmKGYuZW5kc1dpdGgoIi5zb2NrIikpSC5wdXNoKG1ZLmpvaW4oJCxmKSl9Y2F0Y2h7fWxldCBBPWBjbGF1ZGUtbWNwLWJyb3dzZXItYnJpZGdlLSR7ZHpBKCl9YCxMPW1ZLmpvaW4oZ3kudG1wZGlyKCksQSksRD1gL3RtcC8ke0F9YDtpZighSC5pbmNsdWRlcyhMKSlILnB1c2goTCk7aWYoTCE9PUQmJiFILmluY2x1ZGVzKEQpKUgucHVzaChEKTtyZXR1cm4gSH0=", "base64");
const patchBuf = Buffer.from("ZnVuY3Rpb24gWktJKCl7aWYoZ3kucGxhdGZvcm0oKT09PSJ3aW4zMiIpcmV0dXJuWyJcXFxcLlxccGlwZVxcIitROUUoKV07bGV0IEE9YGNsYXVkZS1tY3AtYnJvd3Nlci1icmlkZ2UtJHtkekEoKX1gLEw9bVkuam9pbihneS50bXBkaXIoKSxBKTtyZXR1cm5bTF0gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIH0=", "base64");

if (origBuf.length !== patchBuf.length) {
console.error("FATAL: length mismatch (script bug)");
process.exit(1);
}

console.log("\nReading: " + target);
const bin = fs.readFileSync(target);
console.log("Size: " + (bin.length / 1024 / 1024).toFixed(1) + " MB");

const hashBefore = crypto.createHash("sha256").update(bin).digest("hex").slice(0, 16);
console.log("SHA-256: " + hashBefore + "...");

// Find and patch all occurrences
let patchCount = 0;
let offset = 0;
while (true) {
const idx = bin.indexOf(origBuf, offset);
if (idx === -1) break;
console.log("Found unpatched copy at offset " + idx + " (0x" + idx.toString(16) + ")");
patchBuf.copy(bin, idx);
offset = idx + origBuf.length;
patchCount++;
}

// Count already-patched
let alreadyPatched = 0;
offset = 0;
while (true) {
const idx = bin.indexOf(patchBuf, offset);
if (idx === -1) break;
alreadyPatched++;
offset = idx + patchBuf.length;
}

console.log("\nNewly patched: " + patchCount);
console.log("Already patched: " + (alreadyPatched - patchCount));
console.log("Total patched copies: " + alreadyPatched);

if (patchCount === 0 && alreadyPatched > 0) {
console.log("\n Already fully patched! Nothing to do.");
console.log(" If still not working, restart both Claude Code and Chrome.\n");
process.exit(0);
}

if (patchCount === 0 && alreadyPatched === 0) {
console.error("\nERROR: Could not find the target function in this binary.");
console.error("This patch was written for Claude Code v2.1.37 (function ZKI).");
console.error("Run find-function.js to check your version's function names.\n");
process.exit(1);
}

// Backup
const backupPath = target + ".backup";
if (!fs.existsSync(backupPath)) {
fs.copyFileSync(target, backupPath);
console.log("\nBackup saved: " + backupPath);
} else {
console.log("\nBackup already exists: " + backupPath);
}

// Write patched binary
const patchedPath = target + ".patched";
fs.writeFileSync(patchedPath, bin);

const hashAfter = crypto.createHash("sha256").update(bin).digest("hex").slice(0, 16);
console.log("Patched SHA-256: " + hashAfter + "...");
console.log("\nPatched file written to: " + patchedPath);

console.log("");
console.log("=======================================");
console.log(" PATCH CREATED SUCCESSFULLY (" + patchCount + " copies patched)");
console.log("=======================================");
console.log("");
console.log("Now do these steps IN ORDER:");
console.log("");
console.log(" 1. CLOSE all Claude Code terminal sessions");
console.log(" (type /exit in each, or close the terminals)");
console.log("");
console.log(" 2. Replace the original with the patched file.");
console.log(" In a NEW Command Prompt, run:");
console.log("");
console.log(' copy /Y "' + patchedPath + '" "' + target + '"');
console.log("");
console.log(" 3. CLOSE Chrome completely (all windows)");
console.log("");
console.log(" 4. Reopen Chrome");
console.log("");
console.log(" 5. Open a new terminal and run: claude");
console.log("");
console.log(" 6. Test: ask Claude to look at a website");
console.log("");
console.log("To undo the patch:");
console.log("");
console.log(' copy /Y "' + backupPath + '" "' + target + '"');
console.log("");
console.log("NOTE: 'claude update' will overwrite the patch.");
console.log(" Re-run this script after updating.");
console.log("");

my issue was that there's a compounding problem with Claude Desktop, I created a new issue here, it has a workaround for that too: https://github.com/anthropics/claude-code/issues/24507

when I do both workarounds, now Claude extension works

Thanks for the notice. I had closed down Claude Desktop while I was
trying to get this to work, and this is good reminder that when I reopen
Claude Desktop, my Claude Code may fail once again to connect to the Chrome
extension. Then I'll take a look for that additional workaround.
Thanks again.

On Mon, Feb 9, 2026 at 4:14 PM JasonS @.***> wrote:

jasonswearingen left a comment (anthropics/claude-code#23104) <https://github.com/anthropics/claude-code/issues/23104#issuecomment-3874586913> my issue was that there's a compounding problem with Claude Desktop, I created a new issue here, it has a workaround for that too: #24507 <https://github.com/anthropics/claude-code/issues/24507> when I do both workarounds, now Claude extension works — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/23104#issuecomment-3874586913>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQNQ32T7QQ54HO7Q3LRX2D4LEPIFAVCNFSM6AAAAACT7KB3S6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNZUGU4DMOJRGM> . You are receiving this because you commented.Message ID: @.***>

Anthropic, please fix already. This issue has been open forever!

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.