claude-code - 💡(How to fix) Fix [Bug] Claude redirects browser requests to wrong device on same network [2 comments, 3 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/izotz.cristobal/.local/share/claude/versions/2.1.110 (expected in multi-process scenarios)\n at kU_ (/$bunfs/root/src/entrypoints/cli.js:2751:2153)\n at Mt6 (/$bunfs/root/src/entrypoints/cli.js:2751:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T11:38:33.349Z"},{"error":"McpToolCallError: Failed to read page: Frame with ID 0 is showing error page\n at pf7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T11:43:58.124Z"},{"error":"McpToolCallError: Failed to read page: Frame with ID 0 is showing error page\n at pf7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T11:45:01.233Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T11:45:03.670Z"}]

TL;DR

Check the Claude configuration to ensure it is set up to use the correct Chrome instance on the intended PC.

Guidance

• Verify that Claude is configured to use the Chrome instance on the correct PC by checking the Claude settings or configuration files.
• Ensure that the Chrome extension is installed and enabled on the correct PC.
• Investigate the error messages, particularly the "Lock acquisition failed" error, which may indicate a conflict between multiple Claude instances or processes.
• Check the system logs for any additional error messages or clues that may help resolve the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to the fact that both PCs are connected to the same WiFi network, which could be causing conflicts between the Claude instances. However, without more information, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Check and adjust the Claude configuration to ensure it is using the correct Chrome instance, as this is the most likely cause of the issue.