Codex desktop user reports Markdown file links became plain text
A Codex desktop user reports that Markdown files created or edited by the agent are now returned as plain-text paths instead of clickable file widgets. The user also says separate local or output copies may sometimes be linked, potentially pointing away from the authoritative project file; no confirmed update or cause is provided.
The reported regression could disrupt workflows that depend on opening and editing Codex-generated Markdown files at their actual project paths.
Since today, Codex often returns the path to a Markdown file as plain text instead of the clickable file widget/link it used to provide.
Previously, after an agent created or edited an .md file, I could click the result and open the actual file in the right sidebar. From there, I could read or edit it, and right-click to open its real folder.
Now I usually get only something like:
C:\Users\...\actual-project-folder\document.md
Sometimes the agent creates or links a separate local/output copy instead, which is worse: it is not the authoritative file in my project, so edits and “open containing folder” lead to the wrong place.
This seriously disrupts my workflow because I work with Markdown files constantly. I need Codex to link the existing file at its real path—not merely print the path and not create a duplicate just to make it clickable.
This only started happening today. Agents have suggested that a new app-level file-linking rule prevents them from restoring the old behavior.
Is anyone else experiencing this after a recent update? Has anyone found a way to make Codex consistently open the authoritative local file in the right sidebar again?
submitted by /u/rp_tiago [link] [comments]