[Critical] Copilot Coding Agent on github.com Not Working Properly Anymore #190936
-
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
|
Works for my personal repos, but not for org repos. |
Beta Was this translation helpful? Give feedback.
-
|
Working for 2 weeks without any output for now, and even can't close it.
|
Beta Was this translation helpful? Give feedback.
-
|
💬 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.
-
|
An old discussion that was never addressed, https://github.com/orgs/community/discussions/189951 |
Beta Was this translation helpful? Give feedback.
-
|
This is not a Copilot bug. Your organization has Actions restrictions enabled that block external actions. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.




The orphaned sessions are stuck because the Actions runner was deleted while they were still running. Unfortunately this is not something you can fix yourself through the UI.
Here is what you can do:
Option 1: Wait it out
These sessions usually clear automatically after 24-48 hours. Since yours are already 18+ hours old, they might disappear on their own soon.
Option 2: Contact GitHub Support
If you need them gone faster, open a support ticket and include the session IDs from your browser console logs. They can clean these up for you server-side.
For next time:
Cancel any running agent sessions before deleting the Actions runner. This prevents the orphaned state from happening.
By the way…