Not super useful IMO and potential waste of tokens.
Note that this change reduced token usage significantly for many agent runs 
It moved attaching the current file, to just information about the tab you are on. Should consume way fewer tokens. I will relay this feedback too.
5 Likes
My bad, this is much more useful than attaching all active files however, I donât want a config option to disable this too.
2 Likes
I experience reduced number of tokens when I close âActive Tabsâ in chat.
Is this empirically proven pattern?
This got me thinking whether that overcharging period had anything to do with some version of Cursor sending all open tabs with each prompt or something 
2 Likes
this threw me off - i was used to it defaulting on the file. Whats the difference between a tab and a file? Isnât it the same? Does active tab(S) mean it sends all the files on screen? How can multiple tabs be active? Need more info on all this! Please clarify!
Also when you use agent with Active Tab - it doesnât edit the file. And when you ask why, it says that it doesnât know which file it is. Guidance on the changes please!
3 Likes
+1 on this
+1
just let users decide what is added to context automatically
2 Likes
Agreed! Not only wastes tokens but sometimes confuses the agent that I want it to do something with whatever file happened to be open.
@mark-zs The token usage is minimal as it just references the file name.
@instanceofmel tricky proposition, some users complain if it is not automatically added as it saves them clicks all the time. The current implementation has minimal impact as users can attach what they like but also current tab is just a link to file without having to attach full file.
Interesting thanks for the feedback. How can I know if itâs reading the whole file or just a link? Still would be nice if it was a setting. For people doing pure vibe programming the file that happens to be open is rarely what they actually want the agent to be working on.
1 Like
It used to be a whole file attached in the past. As this lead to excessive context usage we replaced it with a reference to the file since agent is able to efficiently read the content.
The usage really depends on the user. A feature request would be the best way to assess if others are looking for the same feature.
Some vibe code with a single file open and just edit that file including coding features, content etc into same file.
1 Like
Thanks Condor. Can you explain what you mean itâs a âreferenceâ to the open file. How does the agent decide whether to read that fileâs contents into context or not based on just a file name reference?
The reference is a file name. The Agent decides based on your instructions.
I would also like a way to disable this, whether itâs the file contents or the file name. I often browse and read the codebase while the agent works, and when I send it an update or respond to it, it gets whatever I last had open attached. It just recently got confused because I was âreading aheadâ on plans for future work - when it reached a stop point in its current work, I gave it new instructions but the last tab I had open was the future work and it incorrectly started on that instead (which didnât really work, because all of its context was the old task).
For me, this is a constant point of friction: that I have to go manually undo the context add on EVERY new message I send (small target to click, easy to forget) or close all active tabs (throws out MY context), both of which make it harder to work in parallel with the agents.
3 Likes
@Texarkanine that would be a great Feature Requests . While you have shared it here, having a dedicated post helps other user to see it and express interest and for us to see it in one place as well.
Agreed! This is super annoying.
We do have control over this now. The flow is New tab â tabs added by default â hover mouse to remove if you donât want them.
Didnât we used to be able to click and remove some of them? Now it is all or nothing. This would be my feature request: Add delete-from-list per-item âxâ, and not only the main chip hover-to-âxâ:
A feature was requested here Please stop automatically adding âTabâ , so Iâd suggest everyone to drop a like there (and if possible a comment), though it is a bit frustrating that all the traction in this post wouldnât already be enough for something like at least a toggle in the options.
2 Likes
opened a bug request as the dev requested from this feature request, go interact with it!