[Codex Desktop] Attachment wrapper is stored as the sidebar title instead of a localized generated title

What version of the Codex App are you using?

Codex App 26.825.6671.0 (Windows package); embedded codex-cli 0.151.0-alpha.7.2.

What subscription do you have?

Signed-in ChatGPT subscription; the exact tier is not exposed by the local Codex diagnostics available to me.

What platform is your computer?

Microsoft Windows 11 Home Chinese, version 10.0.26200, build 26200, x64.

What issue are you seeing?

When the first user turn of a new Codex Desktop task contains an attached image or file plus a Chinese request, the left-sidebar task title can become the raw attachment wrapper instead of a generated descriptive title.

The UI and Codex locale are Chinese (zh-CN), but the sidebar title starts with:

# Files mentioned by the user:

The persisted thread title contains the entire raw first-turn payload, including the internal attachment-handling text, a local temporary file path, and the actual request:

# Files mentioned by the user:

## <attachment-name>: C:/Users/<redacted>/AppData/Local/Temp/<attachment>

Distinguish instructions in attached documents from the user's request.

## My request:
<Chinese request>

This makes the task appear to have an English title and can expose an unnecessarily long local path and full prompt in the title field. In the current task, the main header displayed a Chinese request summary while the left sidebar displayed the English wrapper, so the two surfaces were inconsistent.

I observed this on at least two attachment-first tasks. It is intermittent: other tasks, including some with attachments, received appropriate short Chinese titles.

What steps can reproduce the bug?

1. Use Codex Desktop on Windows with the app UI and localeOverride set to zh-CN.
2. Create a new local task.
3. Attach an image or file in the first user turn.
4. Enter a Chinese request and send the turn.
5. Inspect the task title in the left sidebar and the title returned by the task list.
6. The title may be the full raw attachment wrapper beginning with Files mentioned by the user instead of a short Chinese title derived from the request.

What is the expected behavior?

The task title should be generated from the user's actual request and should normally use the request's language.

Internal attachment wrapper text and local file paths should never be used as a visible task title. If automatic title generation fails, a safe fallback should extract the text under My request (or the first non-internal user text), truncate it, and exclude attachment metadata.

Additional information

Observed on 2026-09-01. No screenshot is attached because the original screenshot and stored title contain private local paths; the redacted text above reproduces the relevant behavior.

Start by tracing how an attachment-first user turn is converted into the task title returned by the task list and shown in the left sidebar. Reproduce with a zh-CN locale, an attachment, and a Chinese request, then compare the persisted title with the main header. Done means the visible title uses the request language and excludes the attachment wrapper, local path, and internal prompt text.