Kody (GitHub Maintainer) eve Template

Kody is an eve-based GitHub maintainer agent template from Vercel Labs that turns repo upkeep into an email conversation: every Monday it sends a digest of open issues, and you reply to make it act. It also summarizes new pull requests, answers GitHub @mentions, and works delegated issues in Linear, so a solo maintainer can run a repo from their inbox. The template is MIT-licensed, written in strict TypeScript ESM, and deploys to Vercel.

What is the Kody eve template?

Kody is a personal GitHub maintainer agent built on the eve agent framework, published under the vercel-labs organization with an MIT license. It takes a GitHub repository's open issues, pull requests, and @mentions as input and produces email digests, in-thread PR summary comments, issue triage actions, and Linear tasks as output. GitHub and Linear credentials are brokered by Vercel Connect, model access goes through the Vercel AI Gateway, and execution runs in the Vercel Sandbox.

What makes Kody stand out?

The template's differentiators are concrete and Vercel-native: it combines weekly email digests, PR summary comments, GitHub mention replies, Linear delegation, and per-user preference storage in one eve project.

• Weekly issue digest — a cron schedule set to 0 9 * * 1 (Mondays 09:00 UTC) fetches all open issues on the configured DIGEST_REPO, groups them into needs-attention, recent-activity, and stale buckets, cites every issue as #N, and sends the digest by email via the Resend MCP.
• Email-driven issue actions — replies land on a Resend Chat SDK channel with Redis-backed thread state; the agent resolves referenced issue numbers against GitHub and can comment, label, close, or create Linear issues, then answers on the same thread.
• Automated PR summaries — the onPullRequest hook in agent/channels/github.ts posts one orienting comment per new PR describing what it does and why, plus a table breaking down changed files; bot-opened PRs are skipped.
• Linear Agent Sessions — a Linear connector via Vercel Connect plus Linear MCP lets you delegate issues to Kody or ask it to email a summary of an issue from inside Linear.
• GitHub @mention replies — @Kody on an issue or PR produces an in-thread reply from the eve GitHub Channel, cross-referencing Linear when it helps.
• Per-principal preference storage — tools for getting, saving, and clearing preferences live in agent/tools and use a Vercel Blob store keyed to the resolved principal, covering defaults like a preferred email address, digest grouping, and a default Linear team.
• Vercel-native auth and secrets — GitHub and Linear credentials use Vercel Connect with OIDC, Blob and the model authenticate with the project's Vercel OIDC token, and the only static credentials are RESEND_API_KEY and RESEND_WEBHOOK_SECRET.
• Extensible agent structure — agent/ contains channels, connections, schedules, subagents, tools, and SKILL.md-based skills (writing-quality, digest-format, triaging-issues, github-linear-bridging), all editable and hot-reloaded by eve.

Who should use Kody?

Kody is made for freelancers, solo maintainers, and anyone who runs a repository alongside other work and wants to keep maintainer tasks in email. A solo open-source maintainer can triage the weekly digest by replying, a freelancer can let Kody summarize every new PR and answer @mentions across client repos, and small teams on Linear can hand issues to the agent in Agent Sessions. People building with AI coding agents can also point Claude Code or Cursor at the setup instructions in the template's README to scaffold their own deployment.

What can you do with the Kody template?

With the deployed agent you can run the main maintainer loop from email and hand off specialized work to subagents.

• Keep a repo triaged from email: reply to the Monday digest with instructions such as create Linear issues for #1 and #2 and assign them to me, and Kody executes the actions and replies on the same thread.
• Skip PR review notifications: get one orienting summary comment with a changed-files table on every newly opened non-bot PR, without opening GitHub.
• Delegate writing work: pair Kody with the eve content agent template by adding a remote subagent file that uses vercelOidc for deployment-to-deployment auth, then let Kody hand off release notes or announcement posts.
• Run research tasks: use the included researcher subagent, which has its own fresh context session and web-only tools, from within Kody's conversation.

How does deployment work?

The one-click Vercel deploy button provisions a GitHub connector pointed at /eve/v1/github, a Linear connector pointed at /eve/v1/linear, a Vercel Blob store for preferences, and an Upstash Redis store for email thread state, then prompts for RESEND_API_KEY, RESEND_WEBHOOK_SECRET, RESEND_FROM_ADDRESS, DIGEST_REPO, and DIGEST_EMAIL. After deployment you point Resend's inbound webhook at https://your-deployment-url/eve/v1/resend. For manual setup, deploy with eve deploy rather than raw vercel deploy --prod, because the raw command cannot auto-detect the eve framework, and create the GitHub and Linear connectors with the Vercel CLI before attaching their trigger paths.

FAQ

Does Kody send the digest during local development?

No. eve dev never fires schedules on their cron cadence. While running the dev server you can trigger the digest manually with curl -X POST http://localhost:3000/eve/v1/dev/schedules/weekly-digest.

What credentials are required?

GitHub and Linear credentials are brokered by Vercel Connect, while Blob and model access authenticate with the project's Vercel OIDC token. The only static environment secrets are RESEND_API_KEY and RESEND_WEBHOOK_SECRET, plus the sender address RESEND_FROM_ADDRESS and digest settings DIGEST_REPO and DIGEST_EMAIL.

Is the Kody template open source?

The template carries the MIT license shown in the repository badge, and the repository lives under vercel-labs. Running it uses Vercel, Resend, and a Redis store, so live deployment costs depend on those providers.

Can Kody be customized?

Yes. The agent's behavior is described in agent/instructions.ts, the cron expression and subject line live in agent/schedules/weekly-digest.ts, the digest's grouping criteria live in agent/skills/digest-format/SKILL.md, and the PR summary dispatch is controlled by the onPullRequest hook in agent/channels/github.ts. Tools, skills, and the model can be changed, and the agent auto-updates as files are edited.