Copilot remote sessions take a long time to "catch up" to current state #195754
Replies: 11 comments 1 reply
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime ��
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. ⭐ |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as low quality.
This comment was marked as low quality.
This comment was marked as low quality.
This comment was marked as low quality.
This comment was marked as low quality.
This comment was marked as low quality.
-
|
Not sure if this is also part of what you mean, but in longer conversations it takes FOREVER to reach the latest messages. It loads from oldest -> newest which is perplexing. (Accidentally posted as a reply before) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Android
Body
For copilot sessions with lots of turns (or background jobs), the mobile experience of using remote control quickly becomes unusable as the mobile app seems to stop updating and never catches up to current state of the session.
Beta Was this translation helpful? Give feedback.
All reactions