Summary
In Codex Desktop, an older/restored thread did not expose the built-in Codex app thread management tools through tool_search, while another Codex Desktop session was able to use them.
This prevented the agent from renaming the current thread through the intended app connector path.
Expected behavior
When a user asks to rename the current Codex thread, the agent should be able to discover and call Codex Desktop thread management tools, such as:
codex_app.list_threadscodex_app.set_thread_title
Expected flow:
- Use
tool_search to find thread management tools.
- Call
list_threads to identify the active/current thread.
- Call
set_thread_title with the active threadId and the desired title.
Actual behavior
In this older thread, tool_search did not expose any codex_app.* tools.
Search query used:
codex_app.set_thread_title list_threads active thread title
Returned tool namespaces included only:
multi_agent_v1mcp__codex_apps__githubmcp__codex_apps__google_drivemcp__codex_security
No codex_app.list_threads, codex_app.set_thread_title, or equivalent current-thread title management tool was available.
Impact
The agent could only suggest a title, but could not apply it through Codex Desktop's intended app API. The user had to rename the thread manually.
This creates inconsistent behavior across Codex Desktop sessions: another session's agent was able to use codex_app.set_thread_title, while this older/restored session could not.
Notes
This is not a request to edit local Codex storage or a local database directly. The expected path is the safer Codex Desktop app connector / built-in tool API.
Possible areas to investigate:
- Whether older/restored threads miss newly added
codex_app tool injection.
- Whether model switches or thread restores can drop app-level tools.
- Whether
tool_search indexes Codex Desktop built-in app tools consistently across old and new sessions.
Summary
In Codex Desktop, an older/restored thread did not expose the built-in Codex app thread management tools through
tool_search, while another Codex Desktop session was able to use them.This prevented the agent from renaming the current thread through the intended app connector path.
Expected behavior
When a user asks to rename the current Codex thread, the agent should be able to discover and call Codex Desktop thread management tools, such as:
codex_app.list_threadscodex_app.set_thread_titleExpected flow:
tool_searchto find thread management tools.list_threadsto identify the active/current thread.set_thread_titlewith the activethreadIdand the desired title.Actual behavior
In this older thread,
tool_searchdid not expose anycodex_app.*tools.Search query used:
Returned tool namespaces included only:
multi_agent_v1mcp__codex_apps__githubmcp__codex_apps__google_drivemcp__codex_securityNo
codex_app.list_threads,codex_app.set_thread_title, or equivalent current-thread title management tool was available.Impact
The agent could only suggest a title, but could not apply it through Codex Desktop's intended app API. The user had to rename the thread manually.
This creates inconsistent behavior across Codex Desktop sessions: another session's agent was able to use
codex_app.set_thread_title, while this older/restored session could not.Notes
This is not a request to edit local Codex storage or a local database directly. The expected path is the safer Codex Desktop app connector / built-in tool API.
Possible areas to investigate:
codex_apptool injection.tool_searchindexes Codex Desktop built-in app tools consistently across old and new sessions.