openai / openai/codex

[Windows] “Pasted text could not be restored” in Codex App 26.814.41407

Open
#39,413 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

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

26.814.41407

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Windows x64

What issue are you seeing?

Since the recent Codex desktop update around August 17, 2026, pasted text can fail to restore in the composer.

A red error toast appears at the top of the Codex window stating:

Pasted text could not be restored

When this happens, the pasted content is unavailable instead of being restored into the composer.

This appears to involve Codex's pasted-text persistence/restoration path rather than a normal clipboard failure.

What steps can reproduce the bug?
  1. Open the Codex desktop app on Windows.
  2. Open an existing conversation or start a new one.
  3. Copy a block of text from another application.
  4. Paste it into the Codex composer.
  5. Codex attempts to process/restore the pasted content.
  6. A red toast appears: Pasted text could not be restored.
  7. The pasted text is unavailable.
What is the expected behavior?

Pasted text should remain available in the composer and be restored successfully if Codex internally persists or converts it.

Restarting or restoring a Codex session should not make pasted content inaccessible.

Additional information

The issue started after the recent Codex desktop update around August 17, 2026.

I have a screenshot showing the exact error toast: Pasted text could not be restored.

There are older potentially related reports involving Codex's pasted-text attachment system, but those report errors such as Large pasted text could not be attached. This report is specifically about pasted text failing during restoration.

Please let me know if there are specific logs, attachment-state files, or diagnostic output I can provide to help identify the failure.

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

Start by reproducing the failure on Windows x64 using the listed steps, then trace Codex's pasted-text persistence and restoration path. Use the exact “Pasted text could not be restored” toast to identify the failing stage; done means pasted content remains available after processing and session restart or restoration.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.