eve Discord Agent

eve Discord Agent is a Discord community agent template built for the eve framework (from Vercel) that answers mentions in threads, recaps what latecomers missed, and stays silent while community members talk to each other. ## What is eve Discord Agent? eve Discord Agent is a starter template for the eve agent framework that connects an AI agent to a Discord server. It takes Discord messages — direct messages, mentions, and thread replies — as input and produces threaded answers or short message recaps as output. It runs on Vercel, with an experimental Discord Gateway relay deployed as a Vercel Daemon, and is distributed in the eve GitHub repository by Vercel. ## What makes eve Discord Agent stand out? - read_recent_messages tool — a custom tool that reads the channel or thread the person asked in, giving the agent the surrounding conversation context. - catch_up skill — turns recent messages into a short recap covering decisions, open questions, and action items. - no_reply behavior — the agent stays quiet when people in its thread talk to each other instead of answering every message. - web_search — an eve default tool, used for current events and facts. - Experimental Gateway relay — runs as a Vercel Daemon and forwards DMs, mentions, and thread replies to the agent. - Vercel Connect credentials — the Discord bot token is stored via Vercel Connect, keeping it out of your environment variables. - Guided setup — pnpm eve add channel/discord --overwrite signs you in to Vercel, links a project, creates the connector, sets the Interactions Endpoint URL, and enables the Message Content intent. ## Who should use eve Discord Agent? - Discord community moderators: deploy the bot so members can mention it with "what did I miss?" and receive a threaded recap of decisions and action items. - eve framework developers: use the template as a working reference for the Discord channel, the Gateway relay, and Vercel Connect credential handling. - Support teams running a Discord server: give members a way to ask questions in a thread without the bot interrupting side conversations. ## How does eve Discord Agent work? Run pnpm install and then pnpm eve add channel/discord --overwrite, choosing "DMs, mentions, and threads" when prompted. Setup signs you in to Vercel, links a project, requests your Discord bot token, creates a Vercel Connect connector, points the application's Interactions Endpoint URL at the agent, and enables the Message Content intent, then writes the connector ID into agent/channels/discord.ts and daemon/main.ts. Deploy with pnpm eve deploy, open the bot install URL, add it to a server, and mention it with a question. For local development, pull a development OIDC token with vercel env pull .env.local, run pnpm dev, scale the production daemon to zero, and start the relay against eve dev with EVE_URL=http://localhost:2000 node --env-file=.env.local daemon/main.ts. ## Use cases - Catching up after time away: a member mentions the bot in a busy channel and gets a recap of decisions, open questions, and action items from recent messages. - Answering questions in threads: the bot replies in a thread so answers stay out of the main channel flow. - Current-events questions: the web_search default tool lets the agent answer factual questions about recent events. ## FAQ ### Does the bot answer every message? No. The template includes a no_reply behavior so the agent stays quiet when people in its thread talk to each other. If Discord does not allow setup to enable the Message Content intent, setup sets messageContent: false in daemon/main.ts, and people must mention the bot in threads. ### Where are the Discord credentials stored? The bot token is stored through Vercel Connect rather than in your environment variables. Setup creates a connector named after package.json's name, usually discord/eve-discord-agent-template, and writes its ID into the channel and daemon files. ### Can I run the relay locally? Yes. Pull a development OIDC token with vercel env pull .env.local, scale the production daemon to zero, then run the relay against eve dev with EVE_URL=http://localhost:2000 node --env-file=.env.local daemon/main.ts. Every relay receives every message, so two running relays make the agent answer twice.