Cursor extension: message-level fork controls disappeared (possible regression)

Resolved 💬 3 comments Opened Apr 6, 2026 by rebroad Closed Apr 6, 2026

What version of the IDE extension are you using?

openai.chatgpt 26.304.20706 (from ~/.cursor/extensions/openai.chatgpt-26.304.20706-linux-x64/package.json).

Which IDE are you using?

Cursor

What platform is your computer?

Linux

What issue are you seeing?

The “fork” icons/actions that previously appeared in conversation history (allowing fork from an earlier prompt/message) are no longer visible in Cursor.

I used to see explicit fork affordances at prior prompts; those controls have disappeared.

What steps can reproduce the bug?

  1. Open Codex in Cursor.
  2. Open an existing conversation with multiple prior prompts/messages.
  3. Hover or inspect message-level actions where fork controls were previously available.
  4. Observe that no fork action/icon is shown.

What is the expected behavior?

Message-level fork controls should be visible (or discoverable via an equivalent UI path) so a conversation can be forked from a prior message.

Additional information

  • I verified that app-server still documents and exposes thread/fork, so this appears to be extension/UI/integration behavior rather than backend API removal.
  • Version probing so far:
  • v0.116 (exact alpha variant unknown): fork controls were not present.
  • v0.117 and v0.118: not yet tested.
  • If this behavior is intentional, please confirm whether message-level forking in Cursor was removed, gated, or relocated, and what the supported workflow is now.
  • If unintentional, this may be a regression in extension UI behavior or capability gating.

View original on GitHub ↗

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