›_ Codex Issues
Codex Issues / #13470

Keep thread name in sync across CLI and app

Resolved 💬 5 comments Opened Mar 4, 2026 by Astro-Han Closed May 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

When I rename a conversation in Codex CLI, the corresponding conversation title in Codex for macOS does not update. This causes title mismatch across surfaces.

Environment

  • Date observed: 2026-03-04
  • Codex CLI: codex-cli 0.107.0
  • Codex macOS app: 26.303.1606
  • Same OpenAI account used in both CLI and app

Steps to reproduce

  1. Start a new conversation in Codex CLI.
  2. Rename it in CLI.
  3. Open Codex macOS app and locate the same conversation.

Actual behavior

The title shown in the macOS app remains unchanged (old title).

Expected behavior

Either:

  • titles stay consistent across CLI and macOS app, or
  • docs/UI clearly state that CLI and app titles are separate and not synced.

Impact

  • Harder to find the right conversation after switching surfaces.
  • Increased navigation mistakes when many conversations have similar names.

Notes

Official docs use different terms (session in CLI, thread in app). It would help to document cross-surface title sync behavior explicitly.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #11907
  • #12507

Powered by Codex Action

Astro-Han · 5 months ago

Adding evidence links for maintainers, in case this helps triage:

1) Official terminology differs by surface

2) Sync scope in docs appears selective

  • App docs explicitly describe thread sync with IDE extension.
  • The same docs describe shared MCP configuration across app/CLI/IDE.
  • I could not find an explicit statement that conversation title rename is synced between CLI and Mac app.

3) Related public discussions (context)

If expected behavior is "not synced", a short docs note would help set user expectations.
If expected behavior is "should sync", then this issue can be treated as a functional bug.

Astro-Han · 5 months ago

I checked the potential duplicates and I think this issue is related, but not the same:

  • #11907 is primarily about refresh/discovery behavior in the macOS app (new conversations, archived conversations, and turn updates not appearing reliably).
  • #12507 is primarily about being able to continue the same conversation across CLI and app.
  • This issue is narrower: even when the conversation is visible across both surfaces, the title/name does not stay in sync after a rename in CLI.

So this seems closer to a cross-surface title metadata sync issue than a refresh issue or a session handoff issue.

oxysoft · 5 months ago

Related follow-up: #14044\n\nOnce thread titles sync cleanly across CLI/app/web, an optional dynamic-conversation-title capability would probably want to ride the same sync semantics. Otherwise auto-renamed titles could drift across surfaces too.

etraut-openai contributor · 3 months ago

This should now work.