GitHub Mobile has no continuity with Copilot CLI / VS Code sessions

[OBOneProtocol]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot CLI

Body

Summary

GitHub Mobile has no continuity with sessions started in Copilot CLI / VS Code. If I start a Copilot chat/agent session on my laptop, I can't pick it up, view its state, or continue the conversation from the GitHub Mobile app — the two surfaces are completely disconnected.

What I'd expect

Since Copilot sessions (especially longer-running or background agent sessions) are already tied to my GitHub account, I'd expect GitHub Mobile to at least let me:

• View the status/output of an in-progress Copilot CLI or VS Code agent session
• Continue or reply to that same conversation from my phone
• Get a notification when a long-running session finishes, with a link back into it

Why it matters

As Copilot's agent/background-task capabilities grow (multi-step sessions that run for minutes or longer), the lack of any bridge to the mobile app makes it hard to monitor or resume work away from the desktop. Right now GitHub Mobile feels like an entirely separate product from Copilot CLI/VS Code, even though both are tied to the same account and (in spirit) the same assistant.

Has session continuity between GitHub Mobile and Copilot CLI/VS Code been discussed or planned? Happy to provide more detail on the specific workflow if useful.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[OBOneProtocol]

Thanks for the quick acknowledgment! I appreciate the transparency about how feedback gets triaged.

I'd be glad to help move this forward directly — I've been building out multi-agent AI workflows and automation tooling around Copilot CLI (see my profile for recent contributions across Grafana, Prowler, and Career Ops), so I have a solid handle on how Copilot sessions behave in practice. Happy to collaborate on design/scope for session continuity between GitHub Mobile and Copilot CLI/VS Code, or just submit a fix/PR directly if there's an existing issue or component to work from.

Let me know where it'd be most useful and I'll follow whatever process works best (RFC, linked issue, PR, etc.).

[4Raisan]

A useful MVP could separate session identity from the client: give each CLI/VS Code agent run a durable session ID, expose read-only status and the latest event on GitHub.com, and let Mobile send a reply or cancel request through the same session. For safety, replies should show the repository, branch, requested permissions, and last update before sending; notifications could deep-link to the session and distinguish “waiting for approval” from “completed.” A small pilot with status-only viewing and completion notifications would validate the workflow before attempting full cross-client transcript editing.

[OBOneProtocol]

Thanks to @4Raisan for collaborating and jumping on this so quickly!

The proposal to separate session identity from the client via durable session IDs is a sound architectural move; it effectively solves the hand-off problem between VS Code and Mobile. We particularly like the idea of starting with a read-only status pilot to validate the event-flow without the overhead of full state synchronization.
One consideration: for the 'waiting for approval' flow to feel responsive, we'd likely need a robust event-bridge (e.g., a server-sent events or webhook model) so the mobile client can trigger the agent's local event loop in real-time, rather than relying on a polled status view. We're aligned with the session-based approach but suggest focusing the pilot on the latency and reliability of these 'approval triggers' to ensure the cross-client experience feels seamless.

To the GitHub team: we would be happy to coordinate our efforts or partner on a resolution for this that aligns with your existing product roadmap and technical preferences. Let us know how you'd prefer to proceed!