You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a strong -1 for enabling it on nodejs/node. Especially if that also enables unwanted automated PR review.
It doesn´t do that. Agent is a featue that allows org members when clicking the "Copilot Agent" button to let Copilot do things for you. Ie, if I ask Copilot to create an issue, it can do it for me.
Also Copilot PR review is already enabled on nodejs/node btw.
I would suggest that repos that want it can opt-in rather than org-wide
I'm unsure why it'd need to be opt-in. I can achieve the same cloning the repo on VS Code and using my agent there (regardless of repo). The only diff, is wit this option enabled I can do it directly from GH UI.
Abby from Github advised ... here's what we found:
All Node.js maintainers already have Copilot Pro for free through their personal subscriptions, which includes 300 premium requests/month. Copilot coding agent is enabled by default for Copilot Pro users, so there's nothing we need to enable centrally at the org level.
In fact, enabling Copilot Business or Enterprise at the org level would put us on the hook for any overages, so we should avoid that unless we get this approved and set a budget.
Regardless of the path forward I think you would need to allow Copilot Coding Agent access to specific repositories. This is done via:
Settings → Copilot → Coding agent → Control repository access
For GitHub Actions usage, since Node.js repos are public, there are unlimited free Actions minutes (though there is a concurrency limit).
Reacted by Jordan Harband, Claudio Wunder and Matteo Collina
Interesting, didn't know it would be billed on the org? We have it enabled on webpack, @bensternthal can you check if we are actually being billed then? If so, we should disable this.
@ovflowd please create an issue in the webpack project and assign to me. I'd like to document what I find for that project there and not add other project findings to the ticket specific to node.
Activity
ovflowd commentedon Feb 9, 2026
cc @nodejs/tsc cc @mcollina
mcollina commentedon Feb 9, 2026
@bensternthal can you verify if this would be covered by our agreement with GitHub, or we would need to pay?
nschonni commentedon Feb 10, 2026
I would suggest that repos that want it can opt-in rather than org-wide
RafaelGSS commentedon Feb 10, 2026
I have a strong -1 for enabling it on nodejs/node. Especially if that also enables unwanted automated PR review.
ovflowd commentedon Feb 10, 2026
It doesn´t do that. Agent is a featue that allows org members when clicking the "Copilot Agent" button to let Copilot do things for you. Ie, if I ask Copilot to create an issue, it can do it for me.
Also Copilot PR review is already enabled on nodejs/node btw.
ovflowd commentedon Feb 10, 2026
I'm unsure why it'd need to be opt-in. I can achieve the same cloning the repo on VS Code and using my agent there (regardless of repo). The only diff, is wit this option enabled I can do it directly from GH UI.
bensternthal commentedon Feb 10, 2026
Abby from Github advised ... here's what we found:
All Node.js maintainers already have Copilot Pro for free through their personal subscriptions, which includes 300 premium requests/month. Copilot coding agent is enabled by default for Copilot Pro users, so there's nothing we need to enable centrally at the org level.
In fact, enabling Copilot Business or Enterprise at the org level would put us on the hook for any overages, so we should avoid that unless we get this approved and set a budget.
Regardless of the path forward I think you would need to allow Copilot Coding Agent access to specific repositories. This is done via:
Settings → Copilot → Coding agent → Control repository access
For GitHub Actions usage, since Node.js repos are public, there are unlimited free Actions minutes (though there is a concurrency limit).
targos commentedon Feb 10, 2026
https://github.com/organizations/nodejs/settings/copilot/coding_agent
ovflowd commentedon Feb 10, 2026
Interesting, didn't know it would be billed on the org? We have it enabled on webpack, @bensternthal can you check if we are actually being billed then? If so, we should disable this.
bensternthal commentedon Feb 11, 2026
@ovflowd please create an issue in the webpack project and assign to me. I'd like to document what I find for that project there and not add other project findings to the ticket specific to node.
ovflowd commentedon Feb 11, 2026
@bensternthal --> webpack/tsc#99