github / github/copilot-cli

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

Open
#4,569 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:sessions
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the session with copilot --allow-all --remote, then compare GitHub Mobile with GitHub.com using the same live session. The report identifies no repository file or test, so investigate the mobile session-state path rather than CLI prompt delivery. Done means Mobile replaces “Queued for Copilot” and displays the CLI response in real time.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, github, shell
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.