Vercel Connect support in GitHub Tools
GitHub Tools now integrates with Vercel Connect to mint short-lived, scoped GitHub tokens at runtime instead of requiring long-lived personal access tokens. This eliminates the need to store, rotate, or manage secrets while maintaining full feature support through preset scopes and custom tool factories.
now has first-class support for through the new subpath. Instead of storing a long-lived personal access token, your agent mints short-lived, scoped GitHub tokens at runtime from a connector. There is no secret to store, rotate, or leak.GitHub ToolsVercel Connect@github-tools/sdk/connect
Attach a GitHub connector to your project and pick a preset:
For custom tool factories, returns a lazy token provider you can pass to directly.connectGithubTokencreateGithubTools
Get started by creating a and reading the .GitHub connectordocumentation
Presets such as , , and map to Connect scopes automatically, so tokens carry only the permissions the toolset needs.Scopes from presets:
code-reviewissue-triagemaintainerImport from and one file in registers the full toolset with Connect-backed auth.Works with eve:
@github-tools/sdk/connect/eveagent/tools/Override , , or per call to target a specific installation or narrow access to individual repos.Multi-tenant ready:
installationIdrepositoriesscopesDeployments automatically authenticate with the OIDC token. For local development, run and .Zero-config on Vercel:
vercel linkvercel env pull
Source: original entry ↗