Optional toggle to exclude oversized files from Chat context

Feature Requests
1

Description / Problem
I frequently work with very large data files (e.g. 1 GB+ CSVs) in Cursor. When I accidentally link one of these instead of just referencing the path, it soft-locks the chat:

  1. The composer throws a “Connection failed. If the problem persists, please check your internet connection or VPN (Request ID: fdcea8e5-a041-4292-9f69-ce87f1351f23)” error.
  2. Opening a new chat still lets me send messages, but I never get a response.
  3. The only recovery is a full app restart, which loses all my in-memory context.

Because it’s easy to drag-and-drop a folder containing a few giant files, an accidental link is an operator error that can cost me dozens of minutes.

Proposal
Add a Chat-only setting (off by default) that:

  • Automatically ignores (does not upload) any attached file above a user-configurable size (e.g. 50 MB).
  • Optionally honors glob patterns (e.g. *.csv) or a .cursorchatignore file.
  • Shows a one-click warning/toast (“Skipped 2 files > 50 MB”) so you know it happened.

This toggle should live in the Chat/Composer settings panel and apply only to Chat context ingestion—so it won’t interfere with .cursorignore rules for indexing or code-assist features.

Benefits

  • Stability: Prevents soft-locks and disconnect loops when huge files slip in.
  • Performance: Reduces token usage and speeds up context construction.
  • Usability: Provides a safety net against accidental folder drags or multi-file selections.

Thanks for considering! This would save a lot of restarts—and tears—when working on data-heavy projects.