# Browser tab closes (or loses focus) when starting new agent conversation

**URL:** <https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064>\
**Category:** Bug Reports\
**Tags:** browser, agents-window\
**Created:** [July 18, 2026, 8:25am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064 "2026-07-18T08:25:28Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![rognierbenoit](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rognierbenoit/32/33709_2.png) [@rognierbenoit](https://forum.cursor.com/u/rognierbenoit)\
**Post date:** [July 18, 2026, 8:25am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/1 "2026-07-18T08:25:28Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

In Agent window, when starting a new agent conversation, the browser tab closes or loses focus

### Steps to Reproduce

open a browser tab, start a new agent conversation

### Expected Behavior

all tabs should remain opened and keep their focus

### Operating System

MacOS

### Version Information

Version: 3.12.17  
VS Code Extension API: 1.128.0  
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50  
Date: 2026-07-17T02:53:53.006Z  
Layout: Agent Window  
Build Type: Stable  
Release Track: Default  
Electron: 40.10.3  
Chromium: 144.0.7559.236  
Node.js: 24.15.0  
V8: 14.4.258.32-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Darwin arm64 25.5.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [July 20, 2026, 7:57am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/7 "2026-07-20T07:57:23Z")

</div>

This is a recent behavior change rather than the tab actually being closed. Browser tabs are currently scoped to the specific agent/chat that opened them, so starting a new agent conversation shows an empty browser strip. The tab isn’t lost though, it still belongs to the original chat, and switching back to that chat brings it right back.

We’ve had this reported a few times and it’s something we’re tracking. In the meantime, for a page you want available across every chat (like a preview or your app), keeping it in a separate external browser window is the most reliable option today.

There’s an existing thread with more discussion (including a “pin a window” idea a few folks have suggested) here: [New chat window clears open browser tabs](https://forum.cursor.com/t/new-chat-window-clears-open-browser-tabs-plus-glitches-with-browser-tabs-not-showing/165025).

---

<div class="post-metadata">

**Author:** ![rognierbenoit](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rognierbenoit/32/33709_2.png) [@rognierbenoit](https://forum.cursor.com/u/rognierbenoit)\
**Post date:** [July 24, 2026, 8:07am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/8 "2026-07-24T08:07:01Z")

</div>

thank @mohitjain you for your feedback. I have added a comment on the thread.

"I don’t see the rationale behind this feature though : why should the app front browser tab be scoped to a conversation ? the front does not die with the conversation, on the contrary. Plus why should consoles not follow the same logic then ? (please don’t …). Imho consoles and app front, should stay across all conversations.

For context on how I use these tabs : consoles are to build and launch backends et front (at least 3 of them) et at least one browser tab for the app front. I name them so that I can refer to it to the agent for it to read error messages. The first thing I do when coming to a fresh agent window is to set up my working tabs. Hence I once asked to be able to save the tabs configuration; ideally each tab would have its own history but that’s another topic …"

---

<div class="post-metadata">

**Author:** ![jsolly](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jsolly/32/33752_2.png) [@jsolly](https://forum.cursor.com/u/jsolly)\
**Post date:** [July 28, 2026, 11:21am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/9 "2026-07-28T11:21:57Z")

</div>

Noting a nearby but distinct bug we hit on 3.13.21: instead of tabs being scoped _to_ a chat, an agent in a _different project workspace_ could attach to Browser Tabs owned by Home/empty-window (`viewId` contained the other workspace id).

New report: [Agent browser\_tabs attaches to Home/empty-window Browser Tabs from a different project workspace](https://forum.cursor.com/t/agent-browser-tabs-attaches-to-home-empty-window-browser-tabs-from-a-different-project-workspace/166856)

(Also left a note on [New chat window clears open browser tabs; plus glitches with browser tabs not showing](https://forum.cursor.com/t/new-chat-window-clears-open-browser-tabs-plus-glitches-with-browser-tabs-not-showing/165025) .)

---

<div class="post-metadata">

**Author:** ![jsolly](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jsolly/32/33752_2.png) [@jsolly](https://forum.cursor.com/u/jsolly)\
**Post date:** [July 28, 2026, 11:28am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/10 "2026-07-28T11:28:17Z")

</div>

## Same cross-workspace tab leak — logs now attached

Follow-up with sanitized logs / session IDs for the Home↔project browser tab bleed (viewId `stable-browser-session/b23abea01bc4771017b008369920af3f` from a non-Home chat), plus wrong-path MCP staging ENOENT.

Primary report: [166856](https://forum.cursor.com/t/166856)

machineId `45f9fb3f-e7a9-4793-a235-3a7bb93e4e3f` · log session `20260727T152911` · composerId `5acf3d63-e855-475f-80d3-765ec4494774` · data sharing on.

[00-SESSION-IDS.txt](https://forum.cursor.com/uploads/short-url/nle3VAszGvhrUJShzPemM2ZvByq.txt)  
[04-KEY-EXCERPTS.txt](https://forum.cursor.com/uploads/short-url/vSThW9XlNtI0hG7Ckc2nMkeWWCM.txt)  
[cursor-browser-bugs-logs-sanitized.zip](https://forum.cursor.com/uploads/short-url/vpUM7jqnPgEZh2Ax7MNOjlWcyXV.zip)

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [July 30, 2026, 12:23pm UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/11 "2026-07-30T12:23:32Z")

</div>

Totally fair point, and it’s feedback we’ve heard from others. You’re right that if terminals stay across conversations, in-app browser tabs feel like they should behave the same, especially when you’re using them as persistent scaffolding (app front, GitHub, previews) rather than throwaway context for a single chat. This is an issue we’re tracking.

In the meantime, keeping the app front in an external browser window is the most reliable way to have it available across chats. For the “save tabs configuration” ask, the closest open discussion is [Pinning a Browser Window in Agent Window](https://forum.cursor.com/t/pinning-a-browser-window-in-agent-window/164990) - worth adding your specific use case there so the pinning feedback stays in one place.

@jsolly - thanks for the cross-link and the sanitized logs. That looks like a distinct scoping issue on our side, I’ll follow up on your primary thread.

---

<div class="post-metadata">

**Author:** ![William\_Stith](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@William\_Stith](https://forum.cursor.com/u/William_Stith)\
**Post date:** [August 6, 2026, 12:53am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/12 "2026-08-06T00:53:39Z")

</div>

Found this while googling for this bug. Well, you guys describe it as intentional but it _definitely_ feels like a bug to me. I use design mode pretty extensively, and the cursor browser is great for that. But lately I’ve been working with grok-4.5 and with its smaller context window I find it filling up faster, and then I go to start a new agent to continue on my session and get frustrated that the browser tab closes. The terminal doesn’t close - that stays alive so my app is still running on localhost. But now on new agents I have to go and open the browser tab again and navigate back to the page I was working on. Pretty frustrating.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [August 6, 2026, 1:07pm UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/13 "2026-08-06T13:07:49Z")

</div>

Hey @William_Stith you’re not wrong that this feels off. It’s not intended behavior, and it’s an issue we’re tracking. One thing that helps in the meantime: the tab isn’t actually destroyed. It stays with the original chat, so switching back to that conversation brings it (and your page) right back.

For persistence across new agents, adding your design-mode use case here keeps that feedback in one place: [Pinning a Browser Window in Agent Window](https://forum.cursor.com/t/pinning-a-browser-window-in-agent-window/164990).

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [September 14, 2026, 10:50am UTC](https://forum.cursor.com/t/browser-tab-closes-or-loses-focus-when-starting-new-agent-conversation/166064/15 "2026-09-14T10:50:40Z")

</div>

Hey @rognierbenoit,

Thanks for the report, and for the detail on how you use your tabs. A fix for browser tabs disappearing when you start a new agent conversation has landed and will be included in an upcoming version of Cursor (3.21). Once you’re on it, browser tabs you open yourself will stay in the tab strip across new agent conversations, just like terminals do. (Tabs the agent opens for its own browsing still stay with that agent’s conversation.)

It may already be in the latest release by the time you read this, so it’s worth updating and giving it another try. Let me know if you still hit it after that.

cc @William_Stith
