{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih57fq6lcmpmjqytj3vea6c3svs3b6jxpxod47y4lttw4scu2wzh4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mkdmvjqgssu2"
  },
  "path": "/t/codex-desktop-on-windows-with-wsl-agent-breaks-local-image-preview-due-to-windows-wsl-path-mismatch/1379761#post_1",
  "publishedAt": "2026-04-25T17:06:11.000Z",
  "site": "https://community.openai.com",
  "textContent": "I am using Codex Desktop on Windows with the agent configured to run through WSL.\n\nWhen the agent generates or returns a local image path, the chat frontend tries to render the image using a path format that does not match the active agent/runtime environment. Because Windows paths and WSL paths differ, the image preview fails and only the broken image alt text is shown.\n\nExample path mismatch:\n\nWindows-style path:\nC:/Users//Documents/…/image.png\n\nWSL-style path:\n/mnt/c/Users//Documents/…/image.png\n\nObserved behavior:\n\n  * Codex Desktop shows a broken image preview.\n  * The generated image exists locally, but the frontend cannot resolve the path.\n  * This happens when the agent path is configured to WSL, while the renderer appears to expect or emit Windows-style local paths.\n\n\n\nExpected behavior:\n\n  * Codex Desktop should normalize local image paths between WSL and Windows.\n  * If the agent runs in WSL and returns `/mnt/c/...`, the frontend should convert it to `C:/...` or a valid `file:///C:/...` URI before rendering.\n  * Alternatively, the app should document which local image path format is required when using a WSL agent.\n\n\n\nEnvironment:\n\n  * Windows + WSL\n  * Codex Desktop\n  * Agent configured to run from WSL\n  * Local image preview in chat fails\n\n\n\nAttached screenshot shows the broken generated image preview.",
  "title": "Codex Desktop on Windows with WSL agent breaks local image preview due to Windows/WSL path mismatch"
}