🛠 Private Infra Ready: Copilot Coding Agent + Your Self-Hosted Runners (Public Preview) #177903
ebndev
announced in
Copilot News and Announcements
Replies: 1 comment 1 reply
-
|
Hello, this day I face an issue when using self hosted runner : Is codeql a prerequisite now ? Edit: I found 2 ways to fix it:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Copilot coding agent can now run its development environment on your own infrastructure using self-hosted GitHub Actions runners managed by Actions Runner Controller (ARC). That means agent tasks can reach internal packages, private build tooling, or on-prem services that aren’t exposed to the public internet—while still remaining ephemeral, isolated, and automated.
🤖 What This Unlocks
🧩 How It Works (Recap)
Copilot coding agent executes tasks in a GitHub Actions-powered environment. By default we provision hosted runners. Now you can override the environment via
copilot-setup-steps.ymland target an ARC scale set.🔧 Setup Steps
Quickstart: https://docs.github.com/actions/tutorials/use-actions-runner-controller/quickstart
copilot-setup-steps.ymlin the repository (or org standard) to point to your scale set viaruns-on:.🛡️ Security & Isolation Notes
✅ Recommended First Uses
📎 Tips
copilot-setup-steps.ymltemplate at the org level for consistency.📘 Learn More
💬 Feedback
Let us know what’s missing—metrics visibility? multi-arch scale sets? runner health telemetry surfaced in the agent summary? Drop ideas in comments below:
Bring Copilot
to where your code actually lives. 🔐
Beta Was this translation helpful? Give feedback.
All reactions