Codex Desktop can sometimes save and display a garbled thread title instead of a normal auto-generated title.

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop 0.122.0-alpha.1

What subscription do you have?

Not relevant

What platform is your computer?

macOS (Darwin x86_64)

What issue are you seeing?

A thread title became garbled in the Desktop app.

This does not look like a pure UI/font rendering problem. The bad title text was already present in the locally persisted thread title data, and later UI surfaces simply read it back.

The malformed title included obvious corruption/artifacts, including:

• replacement-character corruption (�)
• structured-output residue such as to=final

The first user message in the thread was normal text, so this looks like a bad auto-generated title being accepted and persisted instead of being rejected or ignored.

What steps can reproduce the bug?

I cannot provide a stable deterministic end-user repro yet.

Observed repro:

1. Open a fresh thread in Codex Desktop 0.122.0-alpha.1
2. Send a short first message
3. Wait for automatic title generation
4. In my case, the generated title became garbled

What is the expected behavior?

Thread titles should be saved and displayed as normal readable text.

Malformed title content such as � or to=final should not be persisted or shown as the thread title.

Additional information

From local inspection, the corruption appeared to already exist in persisted thread title data rather than being introduced later by rendering.

If useful, I can share a local sample and a tested fix direction.