Describe the Bug
I think this is a network problem. I’m on starlink. The bug is manifesting on Windows10 and MacOS.
What’s happening is that I’m periodically losing connection to the foreground agent.
Here is a request id of one of the failures:
e4641337-ded2-4b34-a7c5-7a19db2c3d2d
Maybe cursor expects a static ip4 or not ipv6, not really sure what the cause is but it’s been happening since 1.0, which was the first version I used. So it’s always issue for me and not a regression.
Steps to Reproduce
Run cursor on starlink. Put the computers on a wireless eero network. I will mention that my eero network is the original hardware from around 2018.
Fire up a foreground agent. Sometimes they fail. Especially when left along for a while.
Expected Behavior
Foreground agents always work
Operating System
Windows 10/11
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.3.8 (user setup)
VSCode Version: 1.99.3
Commit: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Date: 2025-07-31T21:46:17.109Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
