Vercel Connect support in GitHub Tools

GitHub Tools now has first-class support for Vercel Connect through the new @github-tools/sdk/connect 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.

Attach a GitHub connector to your project and pick a preset:

• 
  Scopes from presets: Presets such as code-review, issue-triage, and maintainer map to Connect scopes automatically, so tokens carry only the permissions the toolset needs.
  
  
• 
  Works with eve: Import from @github-tools/sdk/connect/eve and one file in agent/tools/ registers the full toolset with Connect-backed auth.
  
  
• 
  Multi-tenant ready: Override installationId, repositories, or scopes per call to target a specific installation or narrow access to individual repos.
  
  
• 
  Zero-config on Vercel: Deployments automatically authenticate with the OIDC token. For local development, run vercel link and vercel env pull.
  

For custom tool factories, connectGithubToken returns a lazy token provider you can pass to createGithubTools directly.

Get started by creating a GitHub connector and reading the documentation.

Read more

Continue reading...