claude-code - 💡(How to fix) Fix [Bug] Claude model performance regression: instruction following and task completion degradation [4 comments, 4 participants]

[{"error":"Error: 1: Command failed with ERR_STREAM_PREMATURE_CLOSE: code --force --install-extension anthropic.claude-code\nPremature close \n at kpL (/$bunfs/root/src/entrypoints/cli.js:1687:4046)\n at async IpL (/$bunfs/root/src/entrypoints/cli.js:1687:1435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T10:54:58.932Z"},{"error":"McpToolCallError: Could not connect to Chrome. Check if Chrome is running.\nCause: Failed to fetch browser webSocket URL from http://127.0.0.1:9333/json/version: fetch failed\n at lb9 (/$bunfs/root/src/entrypoints/cli.js:4829:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T12:04:16.408Z"},{"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-25T14:09:28.867Z"}]

TL;DR

Check the Chrome browser connection and ensure it is running, as the error logs indicate a failure to connect to Chrome.

Guidance

• Verify that Chrome is installed and running on the system, as the error message suggests a connection issue.
• Check the system's network configuration and ensure that there are no firewall rules blocking the connection to http://127.0.0.1:9333.
• Review the error logs to identify any patterns or correlations between the errors, such as the ERR_STREAM_PREMATURE_CLOSE error.
• Consider restarting the VSCode terminal or the system to ensure that all processes are properly initialized.

Example

No code snippet is provided as the issue seems to be related to environment configuration rather than code.

Notes

The provided error logs suggest that there are multiple issues at play, including a premature close error and a failure to connect to Chrome. Resolving these issues may require a combination of environment configuration changes and troubleshooting.

Recommendation

Apply workaround: Ensure that Chrome is running and properly configured, and investigate the network configuration to resolve the connection issue. This is recommended as the error logs clearly indicate a connection issue with Chrome.