GitHub Copilot SDK 新增服务器间认证支持
GitHub Copilot supports server-to-server authentication
面向所有基于 Copilot SDK 构建自动化 Agent 或服务的开发者:若你的架构依赖用户个人凭据进行 API 调用,请立即评估迁移至新的服务器间认证模式,以解耦业务逻辑与用户状态并确保用量合规。
GitHub Copilot now supports server-to-server authentication for GitHub Apps installed on organizations, available in public preview. Services and agents built with the GitHub Copilot SDK can now make requests on behalf of an organization without relying on a signed-in user’s credentials. This workload-owned identity helps agents and automated services operate reliably at larger scale without tying their authentication or usage to individual users.
GitHub Copilot 现已支持安装在组织上的 GitHub Apps 的服务器到服务器身份验证,目前处于公开预览阶段。使用 GitHub Copilot SDK 构建的服务和代理现在可以代表组织发出请求,而无需依赖已登录用户的凭据。这种由工作负载拥有的身份有助于代理和自动化服务在更大规模下可靠运行,且不会将其身份验证或使用情况与个别用户绑定。
Developers can give a GitHub App the read-only Copilot Requests organization permission, install the app on an 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. The organization’s model policies, budgets, and spending controls apply.
开发者可为 GitHub App 授予只读的 Copilot Requests 组织权限,将该应用安装到组织中,并将短期安装访问令牌传递给 Copilot SDK。使用情况将归因于拥有该安装的组织并对其进行计费。组织的模型策略、预算和支出控制均适用。
Organization owners can review which apps have access, identify app-attributed usage in AI usage CSV reports using the app_client_id field, and stop an app’s access by suspending or uninstalling it.
组织所有者可以查看哪些应用具有访问权限,通过在 AI 使用 CSV 报告中使用 app_client_id 字段识别归因于应用的使用情况,并通过暂停或卸载应用来停止其访问权限。
To get started, see server-to-server authentication for the GitHub Copilot SDK and managing GitHub App access to your organization’s Copilot.
如需开始使用,请参阅 GitHub Copilot SDK 的服务器到服务器身份验证以及管理 GitHub App 对您组织 Copilot 的访问权限。
更进一步:量化金融体系
看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力