Cursor Chats Hang In 2.2 when using Dev Container

[jennings_fantini]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I cannot seem to use any agent or chat interface on any Cursor version larger than 2.0.77. I am running my code in the dev container, and the network diagnostics on all different HTTP versions do not resolve the DNS, SSL, or HTTP. They stay spinning, and then the chats also just stay hanging “Planning next moves”.

This is not an issue in Cursor version 2.0.77, which is the last one that I have been able to get anything working on.

Update

I was able to get chats working on version 2.1.42. But after that, its all broken…

Steps to Reproduce

1. Open Cursor 2.1.42+
2. Run Dev Container
3. Try to chat

Expected Behavior

Chats to work

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

All of them. Literally tested them all.

Additional Information

Obviously something is wrong with the networking in the newer Cursor versions using dev containers because the DNS cannot be resolved.

Does this stop you from using Cursor

Yes - Cursor is unusable

[jennings_fantini]

Has there been any progress on this bug, tested using 2.2.36 and still Diagnostics can’t resolve HHTP/DNS/SSL.

I really would like to use the new update and improvements, but I cannot use Cursor.

Can a Cursor Team Member please help explain the issue with Cursor and push a fix for this?

[sanjeed5 (Sanjeed)]

Thanks for the follow-up and detailed version info. This has been raised to the extensions team. To help them investigate further, could you share:

1. Are you using the Anysphere DevContainers extension or another one?
2. Does the network diagnostic work correctly on the host (outside the dev container)?
3. Any proxy/VPN/firewall setup on your machine or within the container?

Also, Cursor 2.3 is currently rolling out with various stability fixes - worth testing once it reaches you to see if this is resolved.

[gerwitz (Hans Gerwitz)]

Same problem, here, using the Anysphere extenstion. A simple query to Perplexity will make it clear this is a widespread issue; it’s astonishing how poor devcontainer support seems to be.

Yes, the network diagnostics work correctly on the host.

[jennings_fantini]

Cursor 2. 3 seemed to fix the issue. I was using Anyshpere DevContainers, network diagnostic works outside on the host, there is NO VPN setup.