Chat Model as shared between separated cursor instances

Describe the Bug

:white_check_mark: Check the forum
Yes, I checked the forum and found this issue reported and closed without activity.

:lady_beetle: Bug Description
When working with multiple chats in Cursor β€” even across separate windows β€” changing the selected model in one chat immediately updates the model in all other chats. This breaks the logical separation between conversations and limits flexibility when different chats require different model types.

:camera: Screenshots or Recordings
Not attached, but can provide if needed.

:prohibited: Impact on Usage
This issue significantly interferes with workflow, especially when using different chats for different tasks that benefit from different models. It doesn’t completely block use, but it reduces the usefulness of multi-chat functionality and forces repetitive switching.

Steps to Reproduce

Open Cursor and start multiple chats (e.g., Chat A and Chat B).
In each chat, work on a different task or context.
Change the model (e.g., from claude-4-sonnect to auto) in Chat A.
Observe that the model also changes in Chat B (and all other chats), even if they are in separate windows.

Expected Behavior

Chat A and Chat B have diferent selected models and use this.

Operating System

Windows 10/11

Current Cursor Version (Menu β†’ About Cursor β†’ Copy)

Version: 1.1.4 (user setup)
VSCode Version: 1.96.2
Commit: e86fcc937643bc6385aebd982c1c66012c98cae0
Date: 2025-06-19T02:19:20.052Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @Favio_Leyva and welcome to Cursor Forum

Thank you for the detalied bug report.

Yes the Chat model setting is currently linked to all instances and this is working as intended, but I understand you may prefer different behavior.

There has been already a feature request for this and the Cursor Team is aware.