[FR] Self-Hosted Runner Support

Problem

Organizations with stringent security, compliance, or performance requirements are unable to utilize the Copilot Coding Agent due to the lack of self-hosted runner support. This limitation prevents them from running tasks on their own secure infrastructure, leading to:

• Inability to meet strict regulatory compliance.
• Concerns regarding highly confidential codebases.
• Limitations on task duration and execution speed compared to dedicated hardware.
• Makes the product unusable for organizations with strict self-hosted runner mandates.

Solution

Implement support for self-hosted runners, allowing the Copilot Coding Agent tasks to be executed on an organization's own infrastructure. Additionally, ensure a fallback mechanism is in place so that if a self-hosted runner is unavailable, the system defaults to using GitHub-hosted runners.

Benefits

• Enhanced Security & Compliance: Enables organizations to meet strict security requirements and handle highly confidential data within their own controlled environments.
• Improved Performance: Allows for potentially longer task durations and faster execution by leveraging dedicated, optimized hardware.
• Broader Adoption: Makes the Copilot Coding Agent accessible to a wider range of organizations, including those with stringent self-hosted runner mandates.
• Scalability for Small Companies: Provides a vital option for smaller companies looking to scale their use of the agent while maintaining control.
• Increased Reliability: The fallback mechanism ensures continuous operation even when self-hosted runners are not available, preventing disruptions to workflows.

https://github.com/orgs/community/discussions/159068#discussioncomment-13204461

[nhu-do]

Thank you for the detailed write up @abhi-parate-st3 ! Our team is actively discussing a path forward here, and your feedback is helpful as we shape what the end to end experience for self hosted runners can look like.

[beingminimal]

Please consider this feature it will help so many small companies and teams to leverage Copilot Coding Agent (CCA). Thanks

[zdenda-balcar-clevertify]

I’d like to add my support for enabling self-hosted runner support in Copilot Coding Agent. My main reasons are:

1. Lower costs – we operate our own GPU servers (and CPU machines), so using self-hosted runners would significantly reduce expenses compared to GitHub-hosted per-minute rates, especially for longer runs and complex tasks.
2. Full control over the environment – we need specific CUDA versions, drivers, or SDKs (e.g., DeepStream) that aren’t always available on GitHub-hosted GPU instances. With a self-hosted runner, we could manage exactly what’s installed.
3. Improved latency and security – our self-hosted machines run inside a private network with direct access to internal data. Using GitHub-hosted runners forces more complex data transfers and additional security configurations.
4. Long-term scalability – since we maintain our own infrastructure, we can scale capacity as needed and leverage idle GPU/CPU resources without being pushed into a more expensive GitHub Actions tier.

Adding self-hosted runner support would allow us to integrate Copilot Coding Agent more seamlessly into our existing workflows and save both time and money. Thanks for considering!

[beingminimal]

@nhu-do Any hopes or ETA?

[beingminimal]

@nhu-do Any hopes or ETA?

@nhu-do Any update on this feature, please let us know. Awaiting your response. Thanks

[nhu-do]

Hi @beingminimal self hosted runners is a very common feature request. We have pulled this request into our roadmap, and hope to ship this within the next few months.