›_ Codex Issues
Codex Issues / #26233

Codex Desktop/App no longer exposes a thread pinning tool to assistants

Open 💬 2 comments Opened Jun 3, 2026 by KachurPro
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

Codex Desktop/App previously exposed a background thread pinning capability to assistants through tool discovery, under codex_app.set_thread_pinned. In current Codex Desktop/App sessions on codex-cli 0.136.0, that tool is no longer discoverable, and I could not find a documented replacement in the Codex App Server API.

This makes it impossible for an assistant to satisfy a direct user request such as "pin this chat" or a repository boot instruction that asks new Codex threads to pin themselves.

Expected behavior

When a user asks Codex Desktop/App to pin the current chat/thread, the assistant should have a callable, discoverable capability to do that, for example the old shape:

codex_app.set_thread_pinned({ threadId: CODEX_THREAD_ID, pinned: true })

If this capability was intentionally replaced, the replacement should be documented and discoverable by the assistant.

Actual behavior

  • codex --version: codex-cli 0.136.0
  • Searching for set_thread_pinned, codex_app, pin, and pinned thread through tool discovery returns no thread-pinning tool.
  • The public Codex App Server API documents thread methods such as thread/name/set, thread/archive, thread/unarchive, and thread/metadata/update, but I do not see a pin/unpin endpoint.
  • Generated App Server bindings for this version also do not appear to contain a pinned, favorite, bookmark, or equivalent thread property/method.

Repro steps

  1. Start a Codex Desktop/App thread.
  2. Ask the assistant to pin the current thread, or provide a repo instruction that asks the assistant to pin new threads during boot.
  3. Have the assistant search available tools for thread pinning.
  4. Observe that there is no callable codex_app.set_thread_pinned tool and no obvious documented replacement.

Impact

Users cannot automate pinning important Codex Desktop/App threads from chat or from persistent repo instructions. The assistant has to report that pinning is pending instead of completing the request.

Proposed fix

Please restore a discoverable assistant-callable thread pinning capability in Codex Desktop/App, or expose an equivalent App Server method such as thread/pin/set. The method should accept a real thread id and a boolean pin state, and it should be reachable from the assistant when operating inside the current Codex Desktop/App thread.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #25204

Powered by Codex Action

KachurPro · 2 months ago

Additional context from a Codex Desktop/App remote-workspace workflow:

  • Regression window: this worked in codex-cli 0.135.x; in codex-cli 0.136.0 the assistant no longer gets a discoverable codex_app.set_thread_pinned capability.
  • The affected workflow is Codex Desktop/App controlling a remote SSH workspace. The assistant can identify the current thread and can start a remote thread through App Server thread/start, but cannot pin either the current thread or the newly created thread.
  • Tool discovery for set_thread_pinned, codex_app, pin, pinned thread, create_thread, and related thread-management names does not expose a pinning tool in 0.136.0.
  • Generated App Server schema/bindings in 0.136.0 include thread/start, thread/read, thread/archive, thread/unarchive, and thread/metadata/update, but no thread/pin/thread/pinned/favorite/bookmark equivalent. thread/metadata/update appears limited to Git metadata, so it is not a replacement.
  • Chat Creator / create-thread also appears regressed in this workflow: it previously launched a usable chat on the user's computer, but in 0.136.0 it no longer starts/targets the expected remote session correctly. The observable symptom is that the assistant can report a created thread, but the normal Desktop/Chat Creator path does not provide a working way to pin it or reliably target the remote SSH session.

Requested behavior:

  1. Restore a discoverable assistant-callable pin/unpin tool, or add an App Server method such as thread/pin/set.
  2. Make Chat Creator / create_thread remote-target aware in Desktop SSH workflows, so a user can create a remote thread and pin it from the assistant without falling back to raw App Server calls.
  3. If the 0.135 API was intentionally removed, please document the replacement and expose it through tool discovery.

This is intended as a bug report / feature request only; no code branch or PR is needed from my side for now.