Skip to content

Vercel Connect support in GitHub Tools

,

Vercel Connect is generally available as of August 25, 2026. Read the launch blog post, changelog, and complete guide for more information.

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:

import { connectGithubTools } from "@github-tools/sdk/connect";
import { generateText } from "ai";


const tools = connectGithubTools("github/my-connector", {
  preset: "code-review",
});


const { text } = await generateText({
  model: "anthropic/claude-sonnet-5",
  tools,
  prompt: "Summarize open PRs on vercel-labs/github-tools.",
});

Review GitHub PRs with a custom agent

  • 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.

Build a software factory with Vercel Connect

Ship a software factory with GitHub and Linear connectors provisioned for you from the first deployment.

Deploy now