Thread names can get out of sync: localStorage override vs Codex thread name (single source of truth)

[puls-com-leon-komarovsky]

CodexMonitor persists renamed thread names in localStorage (codexmonitor.threadCustomNames) in addition to setting the name in Codex via thread/name/set.

If a local custom name exists, CodexMonitor ignores thread/name/updated events (src/features/threads/hooks/useThreadTurnEvents.ts early-return), so renames done outside CodexMonitor (Codex CLI / VSCode / another machine syncing CODEX_HOME) do not show up and the UI can diverge.

Repro

1. Rename a thread in CodexMonitor.
2. Rename the same thread in Codex (outside CodexMonitor) to a different name.
3. CodexMonitor keeps showing the old name because the local override wins (also used when building the thread list in src/features/threads/hooks/useThreadActions.ts).

Expected
Codex thread name is the single source of truth; CodexMonitor always reflects Codex names / thread/name/updated.

Actual
Local custom name can permanently mask Codex updates.

Suggestion

• Remove threadCustomNames persistence and rely only on Codex names (keep rename by calling thread/name/set, with optimistic UI update).
• Optional migration: on startup, push any existing local overrides into Codex once, then clear localStorage.

[Dimillian]

@codex can you fix that?

[chatgpt-codex-connector]

Summary

• Updated thread rename flow to stop persisting local custom-name overrides and keep rename behavior as an optimistic UI update + thread/name/set call to Codex, aligning thread naming with backend state as source of truth. src/features/threads/hooks/useThreads.tsL160-L176
• Simplified thread storage by removing custom-name localStorage hydration/listening and making getCustomName return undefined, so downstream thread list/event logic no longer has a local override to mask Codex updates. src/features/threads/hooks/useThreadStorage.tsL31-L67
• Updated useThreadStorage tests to reflect the new no-custom-name behavior while preserving pin/activity persistence coverage. src/features/threads/hooks/useThreadStorage.test.tsxL29-L119
• Updated the useThreads integration scenario to assert names come from Codex/list responses (second list call returns updated preview), rather than from local custom-name persistence. src/features/threads/hooks/useThreads.integration.test.tsxL1117-L1229

Testing

• ✅ npm run test -- src/features/threads/hooks/useThreadStorage.test.tsx src/features/threads/hooks/useThreads.integration.test.tsx
• ✅ npm run typecheck

Also completed follow-up workflow requirements:

• Committed on the current branch (2e7e09e).
• Created a follow-up PR via make_pr with title “Follow-up: remove local thread-name override persistence”.

View task →