Build a GitHub agent from one of these examples
Each page below is a complete, runnable agent: every file it needs, not just the interesting snippet. They cover the same ground as Frameworks but end-to-end, with a real task, a real preset, and Vercel Connect wired in as the token source.
Pick an example
| Example | Framework | Task | Preset |
|---|---|---|---|
| Stale issue triager | eve extension | Comment on and close inactive issues | issue-triage |
| Release notes generator | AI SDK | Draft release notes from merged PRs | release-manager |
| CI failure bot | Vercel Workflow | Diagnose and report failing workflow runs | ci-ops |
| Issue triage bot | Chat SDK | @mention triage on GitHub, durable multi-turn | issue-triage |
| Manager agent with sub-agents | eve extension | Route requests to specialist sub-agents | code-review, issue-triage, release-manager |
Shorter, single-file snippets (toolpick, evlog, selective approval) live on the Recipes page.
Production eve templates
For larger, production-ready agents, start with one of these complete eve templates:
Software Factory
Foreman takes work from GitHub and Linear through four specialist agents: classifier, analyst, implementer, and reviewer. It finishes with a reviewed draft pull request for a person to approve and merge.
Deploy the Software Factory | Learn More
Incident Response Agent
sre investigates production alerts using live Datadog, GitHub, and Vercel data. It tests hypotheses, records findings with source links, and keeps investigations read-only by default. Start an investigation from Slack, a watched alert channel, or a webhook.
Deploy the Incident Response Agent | Learn More
Both templates use @github-tools/eve-extension and Vercel Connect for scoped GitHub access without long-lived credentials.
Every example uses Vercel Connect
Each example mints its GitHub token from a Vercel Connect connector instead of a long-lived GITHUB_TOKEN: nothing to store or rotate, and scopes derived from the preset. Swap connectGithubTools for createGithubTools({ token: process.env.GITHUB_TOKEN }) if you'd rather manage a PAT yourself, see Tokens & Auth for the trade-offs.
Why not just read the framework pages?
The Frameworks section shows the shape of each integration in isolation. These examples show a complete agent solving one real job: every config file, every env var, the exact preset and approval policy for that job, so you can copy the whole thing and adapt it rather than assembling it from fragments.
External references
Chat SDK
Connect GitHub tools to Chat SDK for durable GitHub, Slack, and Discord bots, a complete PR review agent in about 60 lines of code.
Stale issue triager
Build an eve agent that finds inactive GitHub issues, asks the author for an update, and closes them if nothing comes back, all files included.