Cursor: Codex thread/task rename is not exposed, and forked threads keep the same title as the base thread

Resolved 💬 2 comments Opened Mar 24, 2026 by ParanoidAndrea Closed Mar 24, 2026

What version of the IDE extension are you using?

openai.chatgpt@26.318.11754

What subscription do you have?

Chatgpt Plus

Which IDE are you using?

Cursor

What platform is your computer?

Windows 11

What issue are you seeing?

In the Codex extension inside Cursor, I cannot rename Codex chats/tasks from the UI.

I also see a second issue: when I fork a thread, the fork keeps the same title as the base thread, so the two threads are hard to distinguish. In practice, the fork title appears identical or nearly identical to the original thread title.

This makes the Tasks/Threads list difficult to use when I have multiple related Codex threads.

What steps can reproduce the bug?

  1. Open Codex in Cursor.
  2. Create a thread with a long auto-generated title.
  3. Try to rename it from the Tasks/Threads list or from the thread UI.
  4. Fork that thread.
  5. Compare the fork title with the base thread title.

What is the expected behavior?

  1. There should be a clear rename action for Codex threads/tasks in Cursor.
  2. Forked threads should get a distinct default title, or at least make the fork relationship obvious.
  3. The title shown in the Tasks/Threads list should be easy to distinguish from the base thread.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗