GitHub Copilot adds server-to-server authentication: call the Copilot SDK with a GitHub App installation token, no signed-in user required
Services and agents built on the Copilot SDK can now run as the organization, with usage and billing attributed to it.
// Key points
- In public preview: grant a GitHub App the read-only "Copilot Requests" organization permission, install it on the organization, and pass a short-lived installation access token to the Copilot SDK.
- Usage is attributed and billed to the organization that owns the installation, and its model policies, budgets and spending controls apply.
- Organization owners can review which apps have access, find app-attributed usage in AI usage CSV reports via the app_client_id field, and revoke access by suspending or uninstalling the app.
Builder's takeBackground coding agents have mostly run on some employee's PAT, breaking when that person leaves and billing usage to an individual. With enterprise GitHub App installations GA on October 23, usage metrics split by client on October 25, and now this, the chain is complete: agents run as the organization, on short-lived tokens, with separate billing. Teams with homegrown CI agents can schedule replacing personal tokens.
// Background · from #Coding agents
Full timeline →- Oct 28 GitHub Copilot assisted permissions are generally available: an LLM classifies command, path and URL requests and auto-approves the clearly safe ones
- Oct 28 Claude Code 2.1.311 and 2.1.312: standard-context sessions over 200K tokens now compact and continue, and hooks are capped at 24 concurrent per session
- Oct 27 GPT-6.1 Terra arrives in GitHub Copilot at provider list pricing, enabled automatically under the default model policy