GitHub previews organization-owned authentication for Copilot SDK agents
GitHub announced on October 27 that Copilot supports server-to-server authentication for GitHub Apps installed on organizations, in public preview. Services and agents built with the Copilot SDK can make requests on behalf of an organization without relying on a signed-in user's credentials. Public preview is not a statement of general availability.
Developers give a GitHub App the read-only Copilot Requests organization permission, install it on an organization and pass a short-lived installation access token to the Copilot SDK. The announcement describes a particular app permission and token flow, not unrestricted access for any background service.
Usage is attributed and billed to the organization that owns the installation. Moving authentication away from an individual user does not make inference free or remove the need to review workload costs before deployment.
The organization's model policies, budgets and spending controls apply. An app token does not override those controls or guarantee access to every model available elsewhere in Copilot. Teams should check the organization that owns the installation when reviewing usage.
Organization owners can review which apps have access and identify app-attributed consumption in AI usage CSV reports through the app_client_id field. They can stop access by suspending or uninstalling an app, according to GitHub.
The release adds workload-owned authentication for the specified SDK use case. It does not establish a numeric inference price, an unlimited allowance or a guarantee of uninterrupted service. Access, preview status and organization billing controls remain separate checks for anyone evaluating an automated agent.