The chat model is being changed automatically

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When opening the chat, it is set to composer1, but it changes to GPT-5.2. While sending a message in GPT-5.2, it reverts back to composer1.

If you stop during message sending and change the model from composer1 to GPT-5.2, the model stays as GPT-5.2. If it’s the same chat window, the model does not revert back to composer1.

When creating a new chat, it starts with composer1 again. After sending a message, the model changes to GPT-5.2, but during message sending, it switches back to composer1

Steps to Reproduce

I think it is difficult to reproduce. I checked with the AIAU community, and the same issue has not occurred with the Japanese ambassadors. Although we are on a team plan at the company, the same issue has not occurred with any of the internal members.

Expected Behavior

I would like the selected model to be kept as it is.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.0-pre.8.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: b3c367fafccbf71de3684eec8d7c78b772bb9950
Date: 2026-01-05T08:26:14.389Z
Build Type: Stable
Release Track: Early Access
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

I checked with the AIAU community, and the same issue has not occurred with the Japanese ambassadors. Although we are on a team plan at the company, the same issue has not occurred with any of the internal members.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi,

Thanks for your post on the Cursor forums.

This forum is currently English only, to help ensure most of our users can participate in the discussions and posts submitted here.

Please translate and repost your message in English.

Thanks!

Note: This is an AI-based detection system and sometimes makes mistakes! If your message is in English, this warning can be ignored!

@condor @deanrie

I apologize for the interruption during your busy time. I would appreciate it if you could review this when you have a moment.

Hey, thanks for the report.

This is unusual behavior. We’re not seeing similar reports from other users. To help us investigate, could you share:

  1. Request IDs: Open the chat menu (three dots in the top-right) > Copy Request ID for a few cases where the model switched
  2. Console logs: Open Developer Tools, go to the Console tab, reproduce the issue, and take a screenshot of the logs
  3. Default model settings: Check Cursor Settings > Models. Which models are set as default for the different modes?
  4. Try another workspace: Create an empty folder and open it in Cursor. Does the issue happen there too?

Also try:

  • Sign out and sign back into your account (Cursor Settings)
  • Reset chat settings: CMD+Shift+P > Preferences: Open User Settings (JSON), then remove any sections related to chat or models

Let me know what you find. This will help the team dig into it.

Thank you for your response.
I will provide answers to each item below.

1: b7cb62c3-49a8-49f9-93cc-6fa6f8d2c76b
58a1656a-c2d5-49a1-90d6-18378aa33699
91ee3544-c67d-4d24-b1fc-8f03cf1bb27c

2: Console log: Open the developer tools, go to the console tab, reproduce the issue, and take a screenshot of the log.
I am unsure how to do this within the editor, so I would appreciate it if you could kindly advise me on how to proceed.

3: There is no model set by default for each mode.

4: The issue is occurring.
I signed out of my account and signed back in, but the issue was not resolved.
Uninstalling the application did not resolve the issue either.

I will send you a video of the actual behavior, and I would appreciate it if you could review it.

If it seems difficult to resolve the issue, you are welcome to log in using my account.
In that case, I would appreciate it if you could contact me at my email address.

画面収録 2026-01-04 0.34.31.zip (1.2 MB)

Thanks for the info. Yeah, this is a known issue that showed up over the last few days and has affected several users. The team is working on a fix with high priority.

Related reports:

The fix should be out soon. Thanks for your patience.

Thank you for your prompt response.
I am looking forward to the release of the updated version.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.