Agents Window opens a second chat for work already running

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since upgrading from 3.13.25 to 3.14.7 (macOS, Agents Window), Cursor often starts a new Agent chat with the same question while another chat is already handling it. I did not click Multitask.
It started after the upgrade. In logs I now see:
GlassTabPersistenceService … reason=“unsupported_tab_kind:agentChat”
(from empty-state-draft → new agent id)
That reason did not appear before 3.14.7. First hit: 2026-08-01 15:38.

Steps to Reproduce

Steps to reproduce:

  1. Use Agents Window on Cursor 3.14.7 (macOS).
  2. Start an Agent chat and let it run on a question.
  3. Without closing that chat, open a new Agent composer (or send a related follow-up / screenshot about the same topic).
  4. A second Agent tab often opens instead of continuing the first one.

Expected Behavior

Expected behavior:
When an Agent chat is already open and working on a topic, Cursor should keep using that chat. A new Agent tab should only open when I explicitly start a new chat — not automatically for the same / related question.

Actual behavior:
A second Agent tab opens for the same work.

Operating System

MacOS

Version Information

Version: 3.14.7 · OS: macOS arm64 · UI: Agents Window

For AI issues: which model did you use?

Auto

Additional Information

Not 100% every time, but frequent. Happy to share more log lines if useful.

Does this stop you from using Cursor

No - Cursor works, but with this issue

8

Hey @Koen_Roozen
Thanks for the detailed report and the log line - that’s really helpful. What you’re describing isn’t intended behavior, and it’s not something you misconfigured. To pin down exactly when the second agent gets created, could you grab a couple of things next time it happens?

  1. A short screen recording of the moment the second chat opens.
  2. The surrounding log lines around one occurrence (a few lines before/after the GlassTabPersistenceService … unsupported_tab_kind:agentChat entry) — Cmd/Ctrl+Shift+P → Developer: Open Logs Folder, then the Window and Main logs.
  3. Whether it happens in the maximized/full editor view, and whether the running agent is a local (“This Mac”) or cloud agent.

Once I can see the exact sequence I’ll get it to the right folks. Appreciate the help narrowing it down!

9

Hi Mohit,###

Environment- Cursor: 3.14.7 (macOS Darwin 24.6.0, arm64)

  • UI: Agents Window / Glass (glassMode = true). I usually work in the Agents Window (not classic sidebar-only chat). Happy to confirm “maximized/full editor” on the next reproduction if that means a specific layout toggle.
  • Agent type: Local (“This Mac”) — not cloud agents when this happens.
  • Regression: started after upgrade 3.13.25 → 3.14.7. First unsupported_tab_kind:agentChat in retained logs: 2026-08-01 15:38.

Screen recording

Attached.

Log note (finding “Window” / “Main”)

On my machine there is no file literally named Window. Session folder: ~/Library/Application Support/Cursor/logs/20260801T144958/

  • Main → attached

  • Window → folders like window1_wb23/ / window1_wb19/ → inside those, the relevant file is renderer.log

The GlassTabPersistenceService / unsupported_tab_kind:agentChat lines are in those renderer.log files (not in alwaysLocalSingleton.log, which is empty).

Latest occurrence (2026-08-03 ~09:11 local)

Same pattern as before: transition from empty-state-draft → new targetAgentId, active tab is diff / stable-diff, Agent chat tab skipped as unsupported.

window1_wb23/renderer.log (around the hit):

2026-08-03 09:09:19.418 [error] Timed out resolving the agent workspace after 30000ms: WorkspaceResolutionTimeoutError: Timed out resolving the agent workspace after 30000ms

2026-08-03 09:11:48.956 [warning] [GlassTabPersistenceService] migration_tab_transition.tab_skipped {“transitionId”:“662c9b00-6be0-4940-9663-2e4aa944c707”,“sourceAgentId”:“empty-state-draft”,“targetAgentId”:“7fe8d0ae-72b2-49bb-88bb-1fe566b5ec89”,“sourceWorkspaceId”:“c434f3c67b7e561117253ffa11f1e4ee”,“activeTabId”:“stable-diff”,“activeTabKind”:“diff”,“reason”:“unsupported_tab_kind:agentChat”,“activeTabSkipped”:false,“tab”:{“tabId”:“agent-chat:empty-state-draft”,“kind”:“agentChat”,“ownerAgentId”:“empty-state-draft”,“preview”:false,“transient”:false}}

Same timestamp in window1_wb19/renderer.log:

2026-08-03 09:11:48.956 [warning] [GlassTabPersistenceService] migration_tab_transition.tab_skipped {“transitionId”:“87f2643c-b6ec-4257-afd7-6ad668ea7aec”,“sourceAgentId”:“empty-state-draft”,“targetAgentId”:“7fe8d0ae-72b2-49bb-88bb-1fe566b5ec89”,“sourceWorkspaceId”:“2ba1ed05bc38271fc944fb416cab8bcb”,“activeTabId”:“stable-diff”,“activeTabKind”:“diff”,“reason”:“unsupported_tab_kind:agentChat”,“activeTabSkipped”:false,“tab”:{“tabId”:“agent-chat:empty-state-draft”,“kind”:“agentChat”,“ownerAgentId”:“empty-state-draft”,“preview”:false,“transient”:false}}

Paired main.log around the same second (new agent-loop wakelock — consistent with a second agent starting):

2026-08-03 09:08:49.503 [info] [PowerMainService] Started wakelock id=666 owner=window:1 reason=“agent-loop” activeCount=1

2026-08-03 09:11:49.044 [info] [PowerMainService] Started wakelock id=667 owner=window:1 reason=“agent-loop” activeCount=2

Frequency (this session folder)- window1_wb23/renderer.log: 6× unsupported_tab_kind:agentChat

  • window1_wb19/renderer.log: 11×
  • window1_wb0/renderer.log: many related promote_noop warnings on empty-state-draft → new agent id

Thanks,

Koen

(attachments)

main.log (368 KB)

Scherm­afbeelding 2026-08-03 om 09.09.03.jpg
Scherm­afbeelding 2026-08-03 om 09.09.03.jpg2990×1860 247 KB

10

Hi Mohit,
I’ve e-mailed you.

rgds Koen

11

We’ve let the team know with this evidence. No timeline to share yet, but I’ll post here when there’s an update. If anything new shows up in the meantime (especially another recording of the exact moment the second chat appears), feel free to drop it here.