feat(Agents Windows): support rename project name like codex app style

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

see the title and screenshot

Screenshot / Screen Recording

企业微信截图_1ccf875d-2d0d-4662-b791-87f624e290f4.png
企业微信截图_1ccf875d-2d0d-4662-b791-87f624e290f4.png1042×524 40.5 KB

Operating System (if it applies)

MacOS

6

image
image778×240 16.1 KB
good news, feat has been supported

7

@deanrie I checked again, and the issue still hasn’t been resolved.

Currently, the Agent window supports renaming conversation/session names under a project, but it still does not support renaming the project name itself.

Supporting project rename would help with two important use cases:

  1. Cursor Agent Window SSH Remote currently does not support worktrees, so when users manually copy multiple versions of the same project, they end up with duplicate project names that are difficult to distinguish.

  2. Some projects contain multiple repos. In practice, users may open a single repo independently in Cursor for focused work. Being able to rename the project would help associate that repo instance with its related parent project more clearly.

8

Hey, thanks for the clarification and the detailed use cases. Both scenarios are clear and valid: SSH Remote without worktrees and multi-repo projects.

Confirmed: right now in the Agents Window you can only rename the session or conversation inside a project. You can’t rename the project group header in the sidebar.

I’ll pass the request to rename the project name to the Glass team as a separate ticket, with a link to this thread and the use cases. I can’t share an ETA.

12

Are there any plans to support？

13

Hey @JimmyLiu, thanks for following up with a question.

Honestly, after an internal review, we decided not to add renaming for the project group header in the Agents Window sidebar for now. We don’t have any plans or an ETA for this specific request right now.

The use cases you described (SSH Remote without worktrees and multi-repo projects) are still valid and make sense, I’m not disputing that. If this is still getting in your way, the best next step is to open a new thread with up-to-date context (your Cursor version and exactly how projects get duplicated or mixed up) so we can take another look with fresh details. A fresh signal really helps when we re-check priorities.

Renaming a session or conversation inside a project still works like before, but renaming the project itself in the sidebar isn’t supported yet.