Github cloud coding agent outage for 10 days 200+ seat enterprise

[dom54]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot Cloud Agent

Body

We are using GitHub Cloud Agent for some use cases at my org, 200+ seats - but have had a few outages . The most recent one is still ongoing after 10 days and no response to tickets no action 3 days after discussing with account manager.

No logs just simply "Failed to launch agent"

My question is..... Am I the only one

[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. ⭐

[jamie-nzfunds]

Similar issue. Switched to a different repo in our organization and ran Copilot Cloud Agent (CCA) - it ran fine. Going back to the problematic repository, the agent just stops very early with "Failed to launch agent", no logs to view.

[maheerCodes]

Based on the other report in this discussion, it does not appear that you are the only one experiencing this issue. Another user has reported that Copilot Cloud Agent works in some repositories but consistently fails with "Failed to launch agent" in a specific repository.

Could you share whether the failure affects all repositories in your organization or only certain ones? It may also help to note whether the issue started after a repository setting change, branch protection update, or Copilot policy change.

Additional details such as repository size, visibility (private/public), and any recent configuration changes could help identify a common pattern while waiting for an official response.

[dom54]

More or less resolved for me now, there is a bug in GitHub hopefully they will fix soon. Remove any copilot environment secrets and agent secrets, defined at the repo level, that could conflict with secrets defined at organisational level

[maheerCodes]

Thanks for the update — this is really helpful for others facing the same issue. Glad to hear it’s resolved.

[maheerCodes]

If this helped clarify the issue, please consider marking it as the accepted answer so others can find it easily.