---
title: "eve GitHub Maintainer"
description: "Maintain GitHub from your inbox with Kody: weekly issue digests, actions by email reply, pull request summaries, and Linear work."
url: "https://vercel.com/templates/eve/eve-github-maintainer"
links:
  repository: "https://github.com/vercel-labs/kody-eve-template"
  deploy: "https://vercel.com/new/clone?demo-title=eve+GitHub+Maintainer&demo-description=Maintain+GitHub+from+your+inbox+with+Kody%3A+weekly+issue+digests%2C+actions+by+email+reply%2C+pull+request+summaries%2C+and+Linear+work.&project-name=kody-eve-template&repository-name=kody-eve-template&repository-url=https%3A%2F%2Fgithub.com%2Fvercel-labs%2Fkody-eve-template&env=RESEND_API_KEY%2CRESEND_WEBHOOK_SECRET%2CRESEND_FROM_ADDRESS%2CDIGEST_REPO%2CDIGEST_EMAIL&envDescription=Resend+API+key+%2B+inbound+webhook+secret%2C+a+verified+sender+address%2C+and+the+digest+repo%2Frecipient.&connect=%5B%7B%22type%22%3A%22github%22%2C%22env%22%3A%22GITHUB_CONNECTOR%22%2C%22triggers%22%3Atrue%2C%22triggerPath%22%3A%22%2Feve%2Fv1%2Fgithub%22%7D%2C%7B%22type%22%3A%22linear%22%2C%22env%22%3A%22LINEAR_CONNECTOR%22%2C%22triggers%22%3Atrue%2C%22triggerPath%22%3A%22%2Feve%2Fv1%2Flinear%22%7D%5D&stores=%5B%7B%22type%22%3A%22blob%22%2C%22access%22%3A%22public%22%7D%2C%7B%22type%22%3A%22integration%22%2C%22integrationSlug%22%3A%22upstash%22%2C%22productSlug%22%3A%22upstash-kv%22%2C%22protocol%22%3A%22storage%22%7D%5D&demo-image=%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2FSP9mlwJlVPo3kWbg0V2RP%2F2d8e131497cf48303657a64542611c93%2Feve-github-maintainer-3x.png"
---

# eve GitHub Maintainer

Maintain GitHub from your inbox with Kody: weekly issue digests, actions by email reply, pull request summaries, and Linear work.

# eve GitHub Maintainer

[eve GitHub Maintainer](https://github.com/vercel-labs/kody-eve-template), named Kody, is an email-centered AI agent for solo maintainers, freelancers, and teams managing a repository alongside other work. It sends a Monday digest of open GitHub issues and acts on your replies. Between digests, it summarizes new pull requests and responds to GitHub mentions or delegated Linear issues.

## What can you build with this template?

The weekly digest fetches open issues and groups them by what needs attention, recent activity, and staleness. Each issue has a linked number you can reference in a reply, such as asking Kody to create Linear issues from two GitHub reports and assign them to you.

Kody resolves the repository and issue numbers before acting. Replies can request comments, labels, issue closures, or cross-linked Linear issues. If it cannot resolve an issue or assignee, its instructions tell it to ask for clarification. It confirms completed work in the same email thread.

You can build AI agents around your maintenance process by editing the digest and triage skills. The included researcher subagent handles questions that need external sources. Standing preferences, such as digest grouping or a default Linear team, persist in Vercel Blob.

## Why use this template?

Kody connects a recurring repository review to the actions that follow it. Maintainers evaluating artificial intelligence agents can inspect the fetched issues behind a digest, then direct tracker updates without opening a separate agent interface.

To choose the best AI agent for repository maintenance, test a real digest reply and review the resulting tracker changes. Kody's email workflow allows routine issue updates without a separate approval prompt, so that behavior should match how you want to delegate maintenance.

## Why use eve on Vercel?

eve's AI agent framework organizes Kody's schedules, channels, and tools. [Vercel Connect](https://vercel.com/docs/connect) handles GitHub and Linear credentials; Blob and AI Gateway use the project's OIDC identity.

Email uses Resend through a Chat SDK channel with Redis-backed thread state. Resend still requires a static API key and inbound webhook secret. You can [adapt the agent's skills](https://vercel.com/kb/guide/how-to-add-eve-skills) to change writing and triage procedures while keeping its email and tracker connections.

## What should you know before deploying?

Deployment provisions GitHub and Linear connectors, Blob storage, and Upstash Redis. Supply the Resend credentials, a verified sender address, and `DIGEST_REPO` and `DIGEST_EMAIL`. The repository and recipient settings are required at build time.

After deployment, manually point Resend's inbound webhook at `/eve/v1/resend` on your deployment so email replies reach Kody. The [repository setup instructions](https://github.com/vercel-labs/kody-eve-template) cover connector registration and local testing.

Reversible issue writes, including comments, labels, and issue creation or closure, ship without approval gates because email cannot render the approval prompt. Configure that list in `agent/extensions/github.ts`. Clearing saved preferences remains approval-gated.

## Frequently asked questions

### What can I do with the weekly issue digest?

Every Monday, Kody emails a grouped view of open issues fetched for that run. Reply with the issue numbers and the changes you want, such as adding a comment or creating linked Linear work. Kody checks the referenced issues before carrying out the request.

### Does Kody review newly opened pull requests?

Kody posts a summary comment based on the pull request's description and diff, with a breakdown of changed files. It skips pull requests opened by bots. This is an orientation for reviewers, not a formal approval or request for changes.

### Who can start work by mentioning Kody on GitHub?

GitHub owners, members, and collaborators can trigger Kody with a mention on an issue or pull request. Other commenters' mentions do not start an agent session. The separate new-pull-request summary trigger can still summarize contributions from outside those roles.

### Can I delegate Linear issues to Kody?

Yes. Delegate an issue or mention Kody in a Linear Agent Session to request work using its Linear tools. For example, ask it to email an issue summary or investigate linked GitHub issues. GitHub-to-Linear work can include links in both trackers.

### Which settings control Kody's repository and write approvals?

You select the digest repository and recipient through `DIGEST_REPO` and `DIGEST_EMAIL`. Routine issue-conversation writes run without confirmation by default; the GitHub extension's approval list is editable. Review those settings before giving the agent access to repositories you maintain.

## Related resources

- [Deploy eve agents on Vercel](https://vercel.com/docs/frameworks/agents/eve)
- [Kody source, configuration, and local development](https://github.com/vercel-labs/kody-eve-template)

## Related Templates

### [eve Contentful Agent](https://vercel.com/templates/eve/eve-contentful-agent)

Manage Contentful from Slack with eve. Query synced content, edit drafts, upload assets, and review publication requests.

### [eve Marketing Team](https://vercel.com/templates/eve/eve-marketing-team)

Coordinate a marketing lead and five specialist agents in Slack, with Notion drafts, Typefully posts, and Resend email campaigns.

### [eve Content Agent](https://vercel.com/templates/eve/eve-content-agent)

Draft content in Slack with house-style skills and Notion sources. Revise in threads and approve new Notion draft pages before creation.

---

## Additional documentation

The [Vercel Knowledge Base](https://vercel.com/kb) contains guides and answers to common questions about Vercel, including deployment, framework configuration, domains, caching, and troubleshooting.
