macOS: Codex in Cursor terminal might receive mangled pasted input
Resolved 💬 3 comments Opened Jan 26, 2026 by emanuelst Closed Jan 26, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.91.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.2-codex (current)
What platform is your computer?
Darwin 25.2.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
Cursor (VSCode Version: 1.105.1)
What issue are you seeing?
When pasting a JSON into Codex inside Cursor’s integrated terminal on macOS, the pasted text might be mangled (characters or keys dropped).
Example: a key customerValidationField becomes customerValidatiField (missing “on”).
Same clipboard paste is correct in Terminal.app and VS Code terminal. Logs show the explicit paste payload already missing characters before Codex processes it.
What steps can reproduce the bug?
- Open Cursor on macOS and start Codex in the integrated terminal.
- Paste a JSON blob.
- Observe that some characters or keys are missing from the pasted text.
What is the expected behavior?
Pasted text should be identical to the clipboard content (no dropped or altered characters / keys).
Additional information
_No response_
3 Comments
Thanks for the bug report. It sounds like you've done some analysis already. Before we jump to a PR, I'd like to understand your analysis of the problem. On the face of it, this sounds like a bug in the Cursor integrated terminal rather than Codex.
I also suspect it might be a Cursor terminal bug (which also seems to be fixed with Cursor Version: 2.4.21 (Universal) VSCode Version: 1.105.1). Since it directly affected pasting into Codex and I couldn’t address it upstream, I tried to fix it in Codex.
We'd prefer not to include workarounds for bugs in other products. That's not maintainable or scalable.
Please report the problem to the Cursor team and work with them to get this fixed. If you have strong evidence that this is an actual bug in Codex, we can revisit this.
In the meantime, I'm going to close this bug report and associated PR.