Allow edit on any message, not just the last one
_PLEASE_ give us the option to edit any previous message, not just forkconversations.
Don't get me wrong, forking is good, it has its place, but editing is much more common, useful, and fast. I don't really feel like polluting the left pane with random edits I made to the conversation, and I equally don't feel like cleaning up when an edit button would be _right there_.
It's already supported in pretty much all coding agents.
So at least an additional edit button would be great.
IMO, the best option would be to allow edit, and fork _internally_, and make the tree available to users (/tree like in Pi, or as a context menu). This is simple and elegant, the most natural UX, keeps the whole tree in a single chat, AND only exposes the complexity (properly) if anybody actually needs it.
---
What steps can reproduce the bug?
Have a couple of back and forth messages. Try to edit an earlier one. You can't.
What is the expected behavior?
Edit message, don't fork, at least not visually.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.415.40636 (1799)
What subscription do you have?
Pro
What platform is your computer?
Mac, Sequoia
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
+1
I'm using Codex Desktop (Windows) and I agree 100%. At least allow us to edit any message. But I agree with the best option, allowing users to view the full tree if/when they want/need it.
That issue is closed, and it refers anyway to the CLI. The current issue is about the desktop app.
Yeah, editing past messages feels like a pretty fundamental feature the app lacks, and I'd imagine it's pretty easy to implement. The tree would absolutely be a really-nice-to-have but probably more effort to implement.
Why is such a basic feature taking so long?
Shouldn't this be a "free" feature given the CLI already provides this functionality?
Why is it still not implemented?