macOS side-panel editor consumes the first Cmd+V after opening an external file
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using?
26.818.41509 (build 6962)
What subscription do you have?
Pro
What platform is your computer?
macOS 26.5.2 (25F84), arm64, Apple M4 Pro
What issue are you seeing?
When a plain-text file outside the active workspace is opened in the Codex Desktop side-panel editor, the first Cmd+V does not insert text. Pressing Cmd+V a second time starts working normally.
This is narrower than #28548: the native shortcut is received and Codex reads the pasteboard, but the first payload is apparently lost before the side-panel editor commits it.
At 2026-09-02 10:47:54.813 +08:00, AppKit logged a keyboard-equivalent action for the Codex process. At 10:47:54.882, the same process requested public.utf8-plain-text, Chromium source metadata, and HTML from the macOS general pasteboard. Codex's ~/.codex/logs_2.sqlite contains no paste, clipboard, or focus event in the surrounding 25-minute window. No related crash was recorded.
No clipboard contents, credentials, tokens, IP addresses, or target-file contents are included.
What steps can reproduce the bug?
- In Codex Desktop, open a local link to a plain-text file outside the active workspace in the side panel. The observed file was a permission-0600
.envfile. - Place the caret after an equals sign.
- Put ordinary plain text on the clipboard.
- Press
Cmd+Vonce. - Observe that no text is inserted.
- Press
Cmd+Vagain. - The paste now succeeds.
What is the expected behavior?
The first explicit Cmd+V should insert the clipboard text when the side-panel editor and caret are visible.
Additional information
- Bundle ID:
com.openai.codex - Codex Framework:
151.0.7922.170 - UI locale:
zh-CN - The macOS unified log proves that Codex requested the plain-text clipboard payload during the failed attempt.
- The target file was eventually modified successfully three minutes later.
- A redacted diagnostic package is available if maintainers need it. It contains only the reproduction report and the relevant unified-log excerpt.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the first-Cmd+V failure in the macOS side-panel editor when opening an external plain-text file, then inspect the external-file opening, editor focus, and pasteboard event path. Use the reported unified-log timestamps and reproduction steps to compare the first and second paste attempts. Done means the first explicit Cmd+V inserts plain text at the visible caret without regressing normal pasting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100