Issue: "Connection stalled" and "NGHTTP2_ENHANCE_YOUR_CALM" errors in large monorepo

Support Bug Reports
, , ,
4

Hey, thanks for the detailed report. I can see you’ve already done a ton of troubleshooting.

NGHTTP2_ENHANCE_YOUR_CALM is a server-side rate limiting error. It can happen when Cursor tries to handle too many requests at the same time. With 53k files (even after filtering), this might be related to how Agent collects context.

A few things to check:

  1. Extensions

A very similar issue with getting stuck on “Planning next moves” was caused by extensions. See this thread: Constantly stuck in "Planning Next Moves" or "Generating...". Try:

CMD + Shift + P > Developer: Open Extension Monitor

Check if any extensions have high CPU or memory usage. If yes, try temporarily running Cursor with --disable-extensions from the terminal.

  1. Extra filtering

53k files is still a lot for Agent mode. Try more aggressive rules in .cursorignore:

# Add these if you haven’t already
**/.nx/
**/dist/
**/build/
**/.turbo/
**/*.test.ts
**/*.spec.ts
**/*.test.py

After changing it, make sure to delete the cache again:

rm -rf ~/.cursor/projects/<project-folder>
  1. Developer Logs

This would help the engineers a lot:

CMD + Shift + P > Developer: Export Logs...

Select Main, Window, Extension Host. You can attach them here, or tell me and I’ll DM you.

  1. Workaround

While this isn’t fixed, you can try working with a smaller part of the code:

  • Open specific subdirectories as separate workspaces
  • Use @Folder mentions to limit scope in Chat

The team knows about this issue, but there’s no timeline yet for a fix for very large monorepos.

Let me know what you see in Extension Monitor and in the logs, it’ll help us dig deeper.