Copilot CLI mobile notifications arrived in GitHub Mobile on July 8, 2026. The latest production app can now surface real-time updates for remote Copilot CLI sessions, helping users see progress and return when an agent needs input.

What GitHub released

GitHub Mobile uses Live Activities on iOS and live update notifications on Android to show a remote session’s current state. Supported states are in progress, waiting for user input, idle, and finished. Tapping an alert opens that session’s logs in the mobile app.

The feature supports remote sessions launched from Copilot CLI, VS Code, and other supported surfaces. Full Live Activities require iOS 17.2 or later, while Android live updates require Android 16 or later; older Android versions still receive agent progress notifications.

Why this matters for QA engineers

Long-running agent tasks such as reviewing flaky-test logs, updating test suites, or analyzing CI failures can pause for a decision or permission request. Mobile status alerts reduce the chance that an unattended prompt leaves the work blocked.

  • Monitor without hovering: check whether the agent is running, waiting, idle, or finished.
  • Respond deliberately: open the session logs before approving file, tool, or URL access.
  • Preserve test evidence: require the final diff, commands run, and CI results before accepting an agent’s changes.

Important limits and controls

The mobile interface does not move execution to GitHub’s servers. GitHub’s documentation says the CLI, shell commands, file operations, and tools continue to run on the machine where the session started. That machine must remain online, and remote control is limited to interactive sessions.

Organization-managed seats also require the applicable Store local sessions in the Cloud policy to allow viewing and control. QA teams should treat remote approvals like desktop approvals: verify the requested scope, avoid broad access, and inspect the resulting test changes.

Bottom line

GitHub Mobile’s new live alerts make remote Copilot CLI work easier to supervise. For QA engineers, the value is faster intervention during long tasks—not automatic trust in the output. Review permissions, diffs, and test evidence before merging.

Sources