Model sees [Pasted Content N chars] placeholder rather than the actual pasted content

Resolved 💬 7 comments Opened Feb 27, 2026 by filipviz Closed Mar 3, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Sometimes (but not always), pasted content is replaced with e.g. [Pasted Content 3525 chars] for the model. An example from a recent rollout log:

{
  "timestamp": "2026-02-27T18:20:45.533Z",
  "type": "response_item",
  "payload": {
    "type": "message",
    "role": "user",
    "content": [
      {
        "type": "input_text",
        "text": "[Pasted Content 3525 chars]\n\nCould you add these to experiments-2/scripts/sweep_static_nu.sh?"
      }
    ]
  }
}

I'm using codex v0.106.0 in ghostty 1.2.3 stable on macOS 26.3. I uploaded an example thread ID 019ca054-65b0-76f2-ab2c-67aa6f745f8d where this happens using /feedback. I've only experienced this in codex v0.106.0.

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #11048

Powered by Codex Action

filipviz · 4 months ago

I can reliably reproduce the issue by following these steps:

  1. Paste more than ~1000 characters into the TUI, triggering the [Pasted Content N chars] placeholder.
  2. In the same input box, press @ to mention a file.
  3. Press tab to tab-complete the filename.

Once you press tab, the placeholder loses its blue color and seems to become plaintext.

etraut-openai contributor · 4 months ago

Thanks for the bug report.

Do you suspect this is a recent regression? If so, do you know which version you started to see this behavior?

filipviz · 4 months ago

I began seeing this behavior after upgrading from codex v0.105 to v0.106 - so yes, I suspect this was a recent regression.

etraut-openai contributor · 4 months ago

OK, thanks. That's really helpful.

etraut-openai contributor · 4 months ago

We understand the root cause. It was a regression, as you suspected. I've posted a PR with the fix.

filipviz · 4 months ago

Thank you for such a quick response and fix!