Typically when I rename a thread it is persistent and remains. Manually naming a thread is best practice for managing multiple agents and context switching cues. Cursor now dynamically renames my threads if one message differs in context even slightly (or relates to a more specific context than the thread is named). This is awful and makes managing context, threads, and multiple agents awful. Please revert this change.
Hey, this is a known bug. Auto naming triggers on the first chat message and overwrites the name even if it was set earlier. Your manual title gets wiped right at that moment.
Workaround: rename the chat after you send the first prompt. Auto rename only runs on the first message, so any name set after that will stick and won’t get reset again. There’s no separate setting to fully disable auto naming yet.
One quick check: you said the rename happens “if even one message differs in context”, meaning it renames mid conversation, not only on the first prompt. If that’s the case, please record a short video. With the current behavior, the chat shouldn’t rename after the first message, so that would be a separate issue.
this is not just renaming in first msg, its renaming even post me naming it custom. its breaking my entire flow. i have names for few threads which it keeps changing randomly. such a dumb feature. where is the toggle to not rename.
Hey, thanks for the details. There might be two different scenarios here, and it’s important to figure out which one you’re seeing.
One known bug is when auto-naming runs on the first chat message and overwrites a name you set before that. Workaround: rename the chat after you send the first prompt. Auto-rename only runs on the first message, so a name set after that should stick. There’s no toggle to fully disable auto-naming yet.
But you’re saying names change even after you manually set them, mid-conversation. With current behavior, that shouldn’t happen. Named chats shouldn’t get renamed on later messages. If that’s what’s happening, it’s a separate issue and I’ll need a bit more info:
Cursor version and OS
A short screen recording showing a chat with a manually set name renaming itself after the first message
The Request ID from a chat where this happened right top chat menu > Copy Request ID
With that, I can dig into what’s going on. Let me know.
I am on the latest version and it renames mid conversation. It’s terrible! haha… Thank you for all the help Dean, always insanely fast replies. Version: 3.11.19
Got it, thanks for the version, Max. That’s enough for me, I’ll log it separately from the first bug: renaming an already named chat in the middle of a conversation, not only on the first message. With the current behavior, this shouldn’t happen. If there’s an update, I’ll reply here.
If you happen to have a short screen recording or a Request ID from a chat where this happens right now (right top chat menu > Copy Request ID), I’d really appreciate it, it’ll speed up the investigation.
Dear Dean , Hey, I have exactly the same problem. On one workspace I have a lot of chats, and the names are essential , I put a lot of care into choosing them. But for about a week now, it’s been renaming itself on its own. My impression is that it happens when the context gets full. I can’t record a video because it happens at a random moment, so there’s no way to predict it in advance, and by the time you notice, it’s already too late.
Hey, thanks for the details. What you’re describing is separate from the first bug rename on the first message. Here the chat is changing a name you already set manually in the middle of the conversation, and with the current logic that shouldn’t happen. A few other users in this thread have confirmed the same symptom.
I get that it’s hard to record a video since it’s random and you can’t predict when it’ll happen. But a recording isn’t required. The Request ID is saved after the fact, so if you catch a chat where the name has already reset:
Open the top-right chat menu > Copy Request ID and paste it here
Also share your Cursor version and OS macOS or Windows
Your note about context filling up is helpful too. The workaround rename after the first prompt won’t help here, unfortunately. It only fixes the first bug. For this one, we don’t have a workaround yet and I can’t give an ETA. If there’s an update, I’ll reply in the thread.