Please stop automatically adding “Tab”

Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

I always delete it manually. Always!!!

Screenshot / Screen Recording

Cursor_PAhi31ah62.png
Cursor_PAhi31ah62.png453×125 6.62 KB

6 Likes
2

hi @sungho that [1 Tab] is just a reference and not the whole tab attached. You can safely continue using Cursor without worrying about the tab.

Let me know if it causes some issues.

2 Likes
3

Please add an option stop attaching A 1 ONE SINGLE TAB.

4

Thank you for the feature request, we will consider it.

1 Like
5

Thank you for your job

1 Like
6

I understood your response to mean that “only the file’s reference (such as its location) is attached, not the entire contents of the file corresponding as a tab.” However, what concerns me is that rule files are automatically attached together. This is because I have many rule files. What about this case? I want to know if it’s similarly optimized. For example, if the attached file as a tab content isn’t checked, the rule files aren’t automatically attached, etc.

7

Rule files that match requirements are attached. If no rule matches, none would be attached.

In general, try to avoid too many and too long rule files as too many rules in a thread may increase chance of AI hallucinating.

This is handled based on the rule file settings and you have 4 options to control if a rule should be added:

1. Always Rules

  • Setting: alwaysApply: true
  • Attachment: Automatically included in every chat
  • Use case: Core project standards, global coding conventions that should apply to all interactions

2. Auto Attached Rules

  • Setting: Defined with globs patterns
  • Attachment: Automatically attached when files matching the glob pattern are referenced in the conversation
  • Example: Rules for frontend components that activate when working in the /components directory

3. Agent Requested Rules

  • Setting: Requires a description field
  • Attachment: The AI agent decides whether to include the rule based on context and relevance
  • Use case: Specialized knowledge or templates that the AI can invoke when appropriate

4. Manual Rules

  • Setting: No automatic attachment settings
  • Attachment: Only included when explicitly mentioned using @ruleName syntax
  • Use case: Specific templates or workflows you want to invoke on-demand
8

@condor just a reference is also an issue, because, as discussed here Is there a way to disable adding `Active Tab` to every chat? - #14 by condor , sometimes we are reading unrelated work to what the agent is doing. Then the agent reads it and gets confused. It just happened today to me. Only for the agent to have the option to read it will make it an issue sometimes.

It’d be great if it was a toggle in the context section in the cursor settings. It is a very annoying and constant friction point.

9

Could you perhaps post a bug report in case it is causing an issue?

10

C’mon man, from going to a feedback post, to a feature post, now you want to jump into a bug post? Is that much bureocracy really needed for a potentially easy update?

1 Like
11

I assumed you may have a bug since Tab does not attach a file but just a name of the file.

We use bug reports that have a specific form in order to provide engineers with most detailed info they need to reproduce an issue as some cases are not reproducible on our end.

1 Like
12

For me the biggest problem with auto adding the tab regardless if its the full contents or just a reference is that it confuses the model that my request has something to do with the tab. More often than not I am asking or requesting things that have nothing to do with the currently open tab/s and it is annoying to have to click remove on every single request I make. Also the tabs get reattached if you change modes too….

1 Like
13

please interact with the bug post i just posted to see this issue resolved Add ability to remove 'Active Tab(s)' to context by default

14

Any Update :smiling_face_with_tear:

15

This seems to be the default behavior now in v2.0.5. Have to manually drag the current tab into the chat to add it to context.

No active tab or any context area by default

image
image437×116 2.61 KB

However, in a new chat, if you ask it what context it has it will tell you that it is aware of what files are open, uncommitted changes, what line your cursor is on and what file is currently active, so even though active tab is no longer automatically added, it doesn’t mean it is not aware of the file you are currently in. When giving a request about making a change, it assumes it is in the current file unless otherwise noted.