openai / openai/codex

[macOS] Composer remains permanently bold after pasting bold rich text; no way to clear formatting

Open
#42,851 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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

26.831.21537

What subscription do you have?

Enterprise

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

On Codex Desktop for macOS, pasting rich text copied from another application when the copied text is already bold leaves the composer in a persistent bold formatting state. The pasted content appears bold, and any text typed immediately afterward also remains bold even though the newly typed text was not copied or explicitly formatted.

There is no standard keyboard escape from this state:

  • Cmd+B cannot disable bold because Codex assigns that shortcut to another app command, such as Toggle Sidebar.
  • Cmd+Shift+V / Edit > Paste and Match Style also fails to clear or reset the composer's bold formatting state.

As a result, the user can become trapped in bold formatting within the composer.

What steps can reproduce the bug?
  1. On macOS, open the Codex desktop app and focus the message composer.
  2. In another application, copy text that is already formatted as bold.
  3. Paste it into the Codex composer.
  4. Place the caret at the end of the pasted text and type additional, previously unformatted text.
  5. Observe that the newly typed text continues to be bold.
  6. Press Cmd+B to try to turn bold off. Codex invokes another command (for example, Toggle Sidebar) instead of toggling bold in the focused composer.
  7. Try Cmd+Shift+V / Paste and Match Style. Observe that it does not clear or reset the bold formatting state.
What is the expected behavior?

Formatting inherited from pasted rich text should not leak into subsequently typed text. After the paste, newly typed text should use the composer's normal formatting unless the user explicitly enables bold.

Cmd+Shift+V / Paste and Match Style should paste without source formatting and reset the insertion point to normal text. The focused composer should also provide a reliable way to toggle bold off; if Cmd+B is reserved for an app command, an equivalent accessible control or context-sensitive shortcut is needed.

Additional information

I searched both open and closed issues before filing and did not find an exact duplicate. Related but distinct reports:

  • #33586 — styled text/html clipboard content is materialized as Markdown, changing pasted code.
  • #34071 — broader report that rich-text support is broken in several ways and cannot be disabled.
  • #34004 — macOS report that pasted diffs are converted/corrupted as Markdown, including with Cmd+Shift+V.
  • #28548 — separate macOS native-menu regression where the Cmd+V accelerator intermittently disappears while Paste and Match Style remains present.

This issue is specifically about the composer retaining the bold insertion state after a bold rich-text paste, causing all subsequent typing to stay bold, combined with both normal escape routes (Cmd+B and Cmd+Shift+V) being unavailable or ineffective.

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

No files or tests are named. First reproduce the issue in the macOS desktop composer using the listed paste and typing steps, then trace the composer’s rich-text paste handling and bold insertion state. Done means pasted bold text does not make later unformatted typing bold, Paste and Match Style resets formatting, and the focused composer has a reliable way to disable bold.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.