codex - 💡(How to fix) Fix Pinned thread state should sync across Desktop and mobile clients

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Pinned thread state should sync across Desktop and mobile clients