Frequent “Cannot reconnect. Please reload the window.” errors after updating to Cursor 3.14.27

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I updated to the latest stable Cursor version this morning. Since the update, I repeatedly receive the following error message:

Cannot reconnect. Please reload the window.

The error occurs irregularly, but approximately every ten minutes. This is particularly disruptive because it interrupts active agentic flows and forces me to reload the Cursor window.

I am working inside a Dev Container. I do not yet know whether the issue is specific to Dev Containers or also occurs in regular local workspaces.

Cursor loses its connection and displays the error message roughly every ten minutes. Any running agentic flow is interrupted.

Steps to Reproduce

I have not yet identified a deterministic reproduction sequence. The problem started immediately after updating to Cursor 3.14.27 and has occurred repeatedly since then while working in a Dev Container.

Is this a known issue with Cursor 3.14.27 or with Dev Containers? Please let me know which logs or diagnostics would be useful for investigating it.

Expected Behavior

Cursor should remain connected and agentic flows should continue without requiring the window to be reloaded.

Operating System

MacOS

Version Information

Version: 3.14.27 (Universal)
VS Code Extension API: 1.128.0
Commit: 047548b00c1a079373d74d00183f32510a4a41e0
Date: 2026-08-04T03:29:11.183Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Additional Information

Dev Containers Plugin:
Identifier: anysphere.remote-containers
Version: 1.0.38
Last Updated: 2026-07-31, 13:02:18

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi @Der_Simon Thanks for the detailed report. I cannot confirm yet that this is specific to Cursor 3.14.27. The message means Cursor’s connection to the Dev Container reached a state it could not recover from, but the message alone does not identify which part failed.

Could you capture the following immediately after the next occurrence?

  1. Press Cmd+Shift+P, run Developer: Export Logs..., and select Main, Window, and Extension Host.
  2. Run Dev Containers: Show Dev Containers Log and capture the section covering roughly two minutes before and after the disconnect.
  3. Run docker inspect --format 'status={{.State.Status}} oom={{.State.OOMKilled}} restarts={{.RestartCount}} started={{.State.StartedAt}}' <container-name-or-id> and share the output.
  4. Let me know whether the same project remains stable for 20 to 30 minutes when opened as a regular local folder.

Please send the full exported ZIP to [email protected] rather than posting it publicly. Redacted log excerpts are fine to post here. Please also include your Docker Desktop version and the container’s Linux distribution. The log export steps are documented here: Agent troubleshooting | Cursor Docs

I do not have a reliable workaround to recommend until the logs show which connection component is dropping. Thank you!

7

Hi @kevinn

Thanks a lot for your reply. I’d be happy to provide log files, but since I reported the issue, it hasn’t occurred again.

I’m assuming it was either a random cluster of incidents or just some kind of temporary hiccup. So I’d suggest we close this thread for now.