›_ Codex Issues
Codex Issues / #25961

Can't edit a message in a side chat (`/side`)

Open 💬 4 comments Opened Jun 2, 2026 by alythobani

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.601.20914 • Released Jun 2, 2026

What subscription do you have?

Plus

What platform is your computer?

Darwin 21.6.0 arm64 arm

What issue are you seeing?

The last-sent message in a /side chat has an edit button on it, which can be clicked to edit the sent message's content (and "Cancel" / "Send" buttons appear within the message, as expected). But clicking "Send" results in a red "Failed to edit message" error (near the top of the app window), with the message still in edit mode and not sent.

What steps can reproduce the bug?

  1. Open a /side chat and send a message
  2. Click the edit button on the sent message, edit something, then click "Send"
  3. Observe the error

What is the expected behavior?

The message is edited and resent

Additional information

_No response_

View original on GitHub ↗

4 Comments

hanzckernel · 2 months ago

I’m seeing a related variant on Codex macOS 26.616.51431.

In a side chat / chat panel, if I send a message and then cancel/stop the running response, the user message cannot be edited afterward. This differs slightly from the original report: I’m not just seeing “Failed to edit message” after clicking Send; after cancellation the edit affordance/path appears unavailable, so I can’t correct and resubmit the cancelled side-chat message.

Expected:
Cancelled side-chat turns should expose the same edit/resubmit behavior as normal completed turns, or at minimum allow editing the last user message.

Actual:
After cancelling the side-chat run, the original message is effectively stuck and I have to type a new message instead.

Environment:

  • Codex macOS
  • Version 26.616.51431 / build 4212
  • Bundle id: com.openai.codex

Feedback ID:
019eb8ee-4363-7393-9764-788e02473603

hulz413 · 1 month ago

Adding another data point from Codex Desktop on macOS.

Environment

  • Platform: macOS / Darwin
  • Codex Desktop release observed in logs: 26.623.101652
  • Date/time reproduced: 2026-07-06 16:24 CST
  • Context: side conversation opened from a local Codex thread

Behavior

Editing the latest user message in a side conversation still fails. After clicking Send on the edited message, the app shows the red toast:

Failed to edit message

The edited message is not submitted.

Relevant local log evidence

At the same time as the toast, the Codex app log shows that the edit path appears to call thread/rollback, which is rejected by the app server:

method=thread/rollback
errorCode=-32600
message="thread rollback requires persisted thread history"

Full nearby log line:

2026-07-06T08:24:32.499Z error [electron-message-handler] Request failed conversationId=019f3685-21d9-7330-85cc-b5f9962a6dd1 durationMs=57 error={"code":-32600,"message":"thread rollback requires persisted thread history"} method=thread/rollback

This makes it look like the side chat edit UI is attempting the normal persisted-thread rollback flow, but side conversations do not have persisted thread history available for that operation.

Expected behavior

Either:

  1. editing/resending the latest side-chat message should work, or
  2. the edit action should be hidden/disabled for side conversations, with a clearer message than the generic Failed to edit message.

There is also a newer duplicate-looking report at #26514.

linear[bot] · 1 month ago

from fc:

Additional dogfood recurrence from #codex-app-feedback on 2026-07-07: Reporter: Ethan Yu Slack: [https://openai.enterprise.slack.com/archives/C09NZ54M4KY/p1783447003716879](<https://openai.enterprise.slack.com/archives/C09NZ54M4KY/p1783447003716879>) Text: "can't edit messages in side chat" No screenshot, feedback UUID, version, or build flavor was included yet. * This looks like the same side-chat edit failure cluster unless follow-up shows a different variant, such as the edit affordance missing entirely rather than Send showing Failed to edit message.
linear[bot] · 1 month ago

from fc:

Follow-up details for Ethan's 2026-07-07 dogfood recurrence: Slack thread: [https://openai.enterprise.slack.com/archives/C09NZ54M4KY/p1783447003716879](<https://openai.enterprise.slack.com/archives/C09NZ54M4KY/p1783447003716879>) Build: 26.706.11357 (4747) Build flavor: internal-alpha Feedback / thread id: 019f2e17-07fd-7350-b4bf-7c0657e3024d User-entered reason: can't edit side chat message Sentry intake status at triage time: Direct event lookup for the UUID returned Event Not Found. Issue search in openai/codex by thread_id:019f2e17-07fd-7350-b4bf-7c0657e3024d and raw UUID returned no results. Issue/error/log searches by exact reason text also returned no results. * Adjacent codex-app, codex-apps, and codex-apps-logging searches by UUID/reason/thread/rollback did not find rows. So this is attached as another current-build recurrence, but raw feedback attachments/log rows were not available through Sentry yet.