GitHub Mobile stays "Queued for Copilot" after remote CLI already responds

Describe the bug

GitHub Mobile does not refresh a remotely controlled Copilot CLI session after submitting a prompt. The mobile app remains at "Queued for Copilot", even though the local CLI receives the prompt and responds immediately. Opening the same session on GitHub.com shows the response and updates correctly in real time.

This appears isolated to GitHub Mobile session state synchronization rather than prompt delivery, CLI execution, or the remote-control connection.

Affected version

• GitHub Copilot CLI 1.0.80
• GitHub Mobile 1.273.0
• Android 16
• CLI host: Debian 13 x86_64

Steps to reproduce the behavior

1. Start a repo-less interactive session with copilot --allow-all --remote.
2. Open that remote session in GitHub Mobile.
3. Submit Hi from the mobile app.
4. Observe that GitHub Mobile displays "Queued for Copilot" and does not show a response.
5. Inspect the local CLI: it received Hi immediately and responded Hi! How can I help?.
6. Open the same remote session on GitHub.com: the response is present and the browser interface updates correctly.

Expected behavior

GitHub Mobile should update the remote session in real time, replace the queued state when the prompt is accepted, and display the CLI response just as GitHub.com does.

Additional context

• The CLI reports remote control connected successfully.
• The Copilot remote service remains active and its GitHub HTTPS connections remain established.
• The CLI log contains no corresponding disconnect or prompt-delivery error.
• Keep-alive is enabled, and the host remains online.
• Related broader report: #2765. This report isolates the failure to GitHub Mobile because the browser works correctly against the same live session.

まず copilot --allow-all --remote でセッションを再現し、その後、同じライブセッションを使って GitHub Mobile と GitHub.com を比較します。報告ではリポジトリのファイルもテストも特定されていないため、CLI プロンプトの配信ではなく、モバイルのセッション状態の経路を調査してください。完了条件は、Mobile が「Queued for Copilot」を置き換え、CLI の応答をリアルタイムで表示することです。