openai / openai/codex

Edit Message and Fork Message missing in newly created IDE conversations

Open
#42,505 1 comment 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the IDE extension are you using?

26.825.51511

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Linux 6.8.0-124-generic x86_64 x86_64

What issue are you seeing?
Problem

Starting on September 3, 2026, all newly created Codex IDE conversations are missing both the "Edit Message" and "Fork Message" actions.
Conversations created before September 3 still show both actions under the same account, workspace, and extension version.

Feedback ID

01a066d3-af79-7a23-a764-a2a9cf4fcb31

What steps can reproduce the bug?
  1. Create a new Codex IDE conversation.
  2. Send a message and wait for the response to finish.
  3. Hover over or open the actions menu for the user message.
  4. Edit Message and Fork Message are both missing.
What is the expected behavior?

Edit Message and Fork Message should remain available after the turn finishes.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the VS Code IDE extension by creating a new conversation and checking the user-message actions after the response finishes. Compare it with an older conversation under the same account, workspace, and extension version; done means newly created conversations again expose both Edit Message and Fork Message.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.