codex - 💡(How to fix) Fix Regression: pasting files from Finder no longer exposes local filename/path to Codex [1 participants]

What version of Codex CLI is running?

codex-cli 0.123.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 25.4.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

mac default terminal (zsh?)

What issue are you seeing?

There appears to have been a recent change in paste behaviour when copying files from Finder into Codex.

Previously, if I copied a file in Finder and pasted into Codex, the paste inserted the filename/path. That was very useful in coding workflows, because the agent could then access the actual local file in the project or elsewhere on disk when I was working in a shared local workspace.

Now, pasting the same file appears to attach the image/file content itself instead, and the original filename is no longer exposed in the conversation. For image files in particular, Codex only sees a generic attachment label such as Image #1 rather than the real local filename.

This is a regression for code-project workflows. A common case is that I prepare or export assets locally, for example screenshots, logos, icons, or other files inside a project directory, and then paste them into Codex expecting the agent to be able to locate and use the file directly. Without the filename/path, the agent cannot reference the actual file in the filesystem, cannot reliably update project code to use that asset, and has to ask me to manually provide the path. That adds friction and breaks a workflow that previously worked smoothly.

In my current case, I was working on an app project with local branded image assets. If paste had still exposed the filename/path, Codex could have directly switched the project to use the correct asset file. Instead, because the paste now hides the filename, the agent could only see a generic attached image and could not know which file in the project it corresponded to.

Please consider either:

1. restoring the previous behaviour where Finder paste exposes the local filename/path,
2. exposing the original local filename/path alongside the attachment metadata in chat, or
3. providing an explicit “paste as file reference/path” option for local files.

For coding agents working against a real local codebase, access to the local filename/path is important, not just the rendered attachment content.

What steps can reproduce the bug?

Uploaded thread: 019dba93-f85e-74a1-855a-7f1db1531098

What is the expected behavior?

No response

Additional information

No response