Pinned thread state should sync across Desktop and mobile clients

Open 💬 1 comment Opened May 30, 2026 by KachurPro

Environment

  • Codex CLI: 0.135.0
  • Workflow: Codex Desktop/App on Mac connected to a remote SSH workspace
  • Same Codex thread opened from tablet/mobile and Desktop

Problem

Pinned thread state appears to be client-local or not synchronized across clients.

I started a Codex thread from tablet/mobile, then opened the same thread from Desktop. The thread was not pinned on tablet/mobile and was not pinned on Desktop. In the agent runtime, the codex_app.set_thread_pinned(threadId, true) capability was also not exposed, so the agent could only report current session pin pending.

Expected behavior

Pinned thread state should be account/thread-level metadata and sync across all clients:

  • Pin on Desktop should appear on mobile/tablet.
  • Pin on mobile/tablet should appear on Desktop.
  • Resuming an existing thread from another client should preserve pinned state.

Actual behavior

Pinned state did not sync between tablet/mobile and Desktop for the same thread.

Why this matters

Users often start threads from mobile/tablet and continue them from Desktop. Pinned threads are used as durable working contexts, so lack of sync makes important sessions easy to lose.

Suggested behavior

Even if agent-side codex_app tools are unavailable in a remote SSH thread, client-side pin state should still sync globally across logged-in Codex clients.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗