The AI Assistant will not see or close all opened tabs when asked
Categories
(Core :: Machine Learning: Frontend, defect)
Tracking
()
People
(Reporter: rdoghi, Assigned: jlewis)
References
(Blocks 1 open bug)
Details
(Whiteboard: [aife])
Attachments
(4 files)
Found in
- Nightly 153.0a1 (2026-06-15)
Affected versions
- Nightly 153.0a1 (2026-06-15)
Affected platforms
- all
Steps to reproduce
- Enable Smart Window.
- Have over 20 tabs opened.
- Open a New Tab and Ask the assistant to close all other tabs.
- Hover over the items from the list and Click them.
Expected result
- All other tabs should be displayed inside the Close panel, and the Ai should be able to close them all.
Actual result
- Some of the Tabs are not visible to the AI and the user cannot close them.
Most of the tabs are displayed in the Close panel and can be closed.
This issue occurs with All 3 AI models.
Regression range
N/A
| Reporter | ||
Comment 1•2 months ago
|
||
Attaching the exported conversation
Updated•2 months ago
|
Updated•2 months ago
|
Comment 4•2 months ago
|
||
| bugherder | ||
Comment 5•2 months ago
|
||
| bugherder | ||
| Reporter | ||
Comment 6•2 months ago
|
||
Hi, This issue seems to still occur on my end, I was asking the AI to close all my other tabs and at least 1 tab is missed, in this case the CNN tab, before it missed a google page.
I have 14 tabs opened including the new tab where I am prompting to close my other tabs, and 1 tab seems to remain opened and it never shows up in the confirmation prompt.
This happens in our latest Nightly ID 20260619040854
Hey Rares, thanks for flagging this. I'm looking into the cause here.
Thanks again for flagging this, I have filed a follow-up here: https://bugzilla.mozilla.org/show_bug.cgi?id=2049510
While my fix lessened the issue around detecting all tabs, there is a deeper issue around how the model produces URL tokens that potentially affects all tools calls and not just this one. Please let me know if you have any further questions, but the remaining fix should solve this.
| Reporter | ||
Comment 9•2 months ago
|
||
Verified as fixed in our latest Nightly 154.0a1 (2026-06-22) , I will verify the remaining issue when the fix for Bug 2049510 lands.
Comment 10•2 months ago
|
||
The patch landed in nightly and beta is affected.
:jlewis, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox153towontfix.
For more information, please visit BugBot documentation.
Updated•23 days ago
|
| Reporter | ||
Comment 11•23 days ago
|
||
Updating the main status flag.
Description
•