GitHub Tools

Install the GitHub Tools extension and Vercel Connect client:

pnpm add @github-tools/eve-extension @vercel/connect

The extension provides the GitHub toolset as a versioned eve package. Use a Vercel Connect connector for short-lived, scoped GitHub tokens, or omit @vercel/connect and authenticate with a GitHub token.

Create and attach a GitHub connector to the Vercel project that runs your agent:

vercel linkvercel connect create github --name my-connectorvercel connect attach github/my-connector --yesvercel env pull

Then mount the extension under agent/extensions/:

import githubExtension from "@github-tools/eve-extension";
export default githubExtension({  connector: "github/my-connector",  preset: "maintainer",  requireApproval: {    mergePullRequest: true,  },});

The filename supplies the github namespace, so tools appear as github__listPullRequests, github__createIssue, and github__addPullRequestComment. The preset automatically limits the connector token to the scopes its tools need.

Choose one or more presets to limit the available tools: code-review, issue-triage, repo-explorer, ci-ops, or maintainer. Every write tool requires approval by default, while read tools do not. Use requireApproval to apply always, once, or an input-dependent policy to individual tools:

import githubExtension from "@github-tools/eve-extension";
export default githubExtension({  connector: "github/my-connector",  preset: ["code-review", "issue-triage"],  requireApproval: {    addPullRequestComment: "once",    mergePullRequest: true,    createIssue: ({ toolInput }) => toolInput?.owner !== "my-org",  },});

For local or non-Vercel deployments, omit connector and set GITHUB_TOKEN; the extension also accepts an explicit token. Prefer fine-grained credentials, expose only the presets the agent needs, and keep approval enabled for writes. See the GitHub Tools eve documentation for token authentication, per-tool overrides, commit attribution, and the complete tool catalog.