Skip to content

Remote control: sessions are read-only on GitHub Mobile/web since legacy remote steering was removed (1.0.110) #5528

Backlog

Description

@MoududAbu

Describe the bug

Since 1.0.110 ("Remove legacy remote steering; cloud sessions and remote connections now require an AHP environment"), sessions shared with /remote on can no longer be steered from GitHub Mobile or github.com. The session shows up in the Agents list but is read-only ("Steering disabled"). The only way to steer it now is from another Copilot CLI via /environments.

That breaks the feature as documented and announced as GA in May (https://github.blog/changelog/2026-05-18-remote-control-for-copilot-cli-sessions-now-generally-available-on-mobile-web-and-vs-code): "monitor or steer it from the GitHub Mobile app or github.com". The docs (https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely) still describe phone/web steering and still mention copilot --remote, which now errors with "--remote was removed".

Affected version

1.0.114 (also 1.0.110+). Works on 1.0.108 with COPILOT_AUTO_UPDATE=false.

Steps to reproduce the behavior

  1. Copilot Pro account (personal, no org policy), Linux.
  2. Run copilot (1.0.114), type /remote on. Output: "Sharing this session through Mission Control".
  3. Open the session in GitHub Mobile or at github.com/copilot/agents.
  4. It's view-only, "Steering disabled", and you can't send a prompt.

For comparison:

  1. COPILOT_AUTO_UPDATE=false npx -y @github/copilot@1.0.108
  2. /remote on. Output: "Remote steering enabled" plus a github.com/copilot/tasks/... link.
  3. Prompts sent from GitHub Mobile are received and answered.

Expected behavior

/remote on on the current version should let me steer the session from GitHub Mobile and github.com, as documented. If not, mobile/web should support AHP sessions before legacy steering is removed, and the docs and the mobile hint should be updated.

Additional context

  • OS: Linux x86_64 (Ubuntu), plus a second machine with the same result
  • Pinning 1.0.108 works around it, but auto-update silently upgrades unless COPILOT_AUTO_UPDATE=false is set
  • GitHub Mobile still suggests "start it with copilot --remote", which no longer works
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions