Android Codex Mobile shows "Directory Unavailable" after Desktop conversation updates

Open 💬 2 comments Opened May 31, 2026 by huishen71

What version of the Codex App are you using (From “About Codex” dialog)?

ChatGPT App 1.2026.118

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS 13.6.3 (MacBook Air M2, 2026)

What issue are you seeing?

Android Codex Mobile shows "Directory Unavailable" after Desktop conversation updates

Environment:

  • Desktop: macOS Codex Desktop, latest version as of 2026-05-31
  • Mobile: Android 16, ChatGPT App 1.2026.118, Codex Mobile Preview

Issue:

  • Projects and conversation lists synchronize correctly between Desktop and Android.
  • After a conversation is updated from Desktop, Android fails to load the conversation content.
  • Directory displays "Unavailable".
  • Task results complete on Desktop but Mobile sometimes stays in "Working..." until exiting and reopening the conversation.

Observations:

  • Old threads display normally.
  • New threads or updates from Desktop trigger "Directory Unavailable" on Mobile.
  • Revoking the Android device and re-pairing restores normal access.
  • The issue occurs even for minimal new test conversations ("hello").
  • Real-time state push appears unreliable, though final results are correct.

Temporary Workaround:

  • Revoke Android device in Desktop → re-pair
  • This restores access, but subsequent Desktop updates may trigger the issue again.

Conclusion:

  • Likely related to Android Mobile Preview session refresh / content synchronization rather than project or workspace corruption.

What steps can reproduce the bug?

  1. Pair an Android device with Codex Desktop (macOS).
  2. Open a project from Android; project list and conversation list synchronize correctly.
  3. Open a conversation on Desktop and add new messages or tasks.
  4. Return to the Android device and open the same conversation.
  5. Observe that the conversation content fails to load.
  6. Status page on Android shows "Directory: Unavailable".
  7. Temporary workaround: revoke Android device and re-pair → content loads correctly.

What is the expected behavior?

  • Android device should automatically refresh and display the updated conversation content after Desktop-side updates.
  • Directory should remain available.
  • Task statuses should update in real-time without requiring exiting and re-entering the conversation.
  • New and existing threads should be fully readable immediately after changes on Desktop.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗