Codex Windows app: clicking Codex mobile page auto-navigates back to chat

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

26.527.3686.0 (OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0; logs also mention release 26.527.31326)

What subscription do you have?

Unknown / not sure

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

When I click "Codex 移动版" / Codex Mobile in the left sidebar, the mobile connection page briefly appears, then the main content area automatically navigates back to the new conversation/current chat page.

The click is accepted and the "Connect your phone to this PC" mobile page renders for a moment. After that, the main panel switches back. Sometimes the sidebar still shows "Codex 移动版" selected while the main content has already returned to the chat screen.

This looks like a desktop app route/state synchronization issue rather than a network or permission problem. Around the reproduction time, local logs repeatedly show browser sidebar owner sync events with ownerRoutePath=/, matching the visible auto-navigation back to the home/new conversation route.

What steps can reproduce the bug?

Feedback ID: 019e82ab-47d7-7b63-921b-4ff2620bcba0

1. Open the Codex Windows desktop app.
2. In the left sidebar, click "Codex 移动版" / Codex Mobile.
3. Observe that the "Connect your phone to this PC" page appears briefly.
4. Wait a moment without clicking anything else.
5. The main view automatically switches back to the new conversation/current chat page.

A screen recording GIF is available showing the mobile page flashing briefly and then being replaced by the chat page.

What is the expected behavior?

The Codex Mobile / "Connect your phone to this PC" page should stay open after it is selected from the sidebar.

Additional information

Observed on 2026-06-01 around 18:11 Asia/Shanghai.

Relevant local log findings:

• Repeated IAB_LIFECYCLE received browser sidebar owner sync entries around the reproduction time.
• These entries include ownerRoutePath=/, which matches the UI navigating back to the home/new-conversation route.
• I also saw computer-use native pipe startup failed, but that appears unrelated to this mobile-page routing issue.

I can provide redacted logs and the screen recording if needed.