eve Coding Agent on Slack

A coding agent template for the eve framework that lets you mention a bot in Slack or on a GitHub issue or pull request, then has it investigate, review, or fix code in an isolated Vercel Sandbox before answering in the thread or opening a pull request.

What is eve Coding Agent on Slack?

eve Coding Agent on Slack is a template built on the eve agent framework that turns a Slack or GitHub mention into a coding task. It takes a mention or comment as input, runs the work in a Vercel Sandbox with git, gh, and TypeScript tooling, and outputs an answer in the thread, a pull request, or a Slack code channel showing repository, branch, diff, and tests. The template ships with eve's built-in code extension and its companion git extension; repository metadata identifies the project as "The Open Framework for Building Agents" (5,844 stars).

What makes eve Coding Agent on Slack stand out?

• Slack code channels — for anything needing a repository, the agent calls open_code_channel, which opens a Slack code channel from the message; the channel's session starts with the thread's conversation and everyone there can talk to the agent without mentioning it.
• Context bar and diff view — after each tool that can change the workspace, the renderer reads every repository under /workspace/repos/ and shows repository, branch, and changed-file count, plus diffs against the base branch including untracked files.
• Scoped credentials — each gh command gets a token scoped to one repository, minted by Vercel Connect; the sandbox sees only a placeholder that is swapped in at the firewall and removed afterward.
• Restricted tools — write_file and the root agent tool are disabled so edits go through the editing tool as small reviewable changes and all writes stay in one session; code__worker is a read-only subagent for independent task slices.
• Skills on demand — code__investigate, code__review, and git__pr load when needed.
• Trusted-commenter gating — only comments from repository owners, members, and collaborators start a GitHub turn.
• Configurable code channels — setting CODE_CHANNELS to false in agent/lib/code-channel.ts keeps all Slack work in the thread and skips code-channel scopes in the generated manifest.

Who is it for?

• Software teams using Slack — move triage and coding work out of threaded chat into a code channel that shows the repository, branch, diff, and test status as the agent works.
• Maintainers on GitHub — comment @<bot name> on an issue or pull request to have the agent investigate, review, or open a pull request, with only owner, member, and collaborator comments accepted.
• eve template developers — customize the model in agent/agent.ts, tone in agent/instructions.md, context-bar items in agent/lib/code-channel.ts, and add skills or tools under agent/skills/ and agent/tools/.

How does it work?

The template wires eve's code and git extensions to Slack and GitHub. Run pnpm install, vercel link, vercel env pull, and pnpm dev to open a dev session. Connect Slack with eve add channel/slack, and create the GitHub connector with vercel connect create, detach, and attach commands routing webhooks to /eve/v1/github. Set GITHUB_ORG, GITHUB_CONNECTOR, and GITHUB_BOT_NAME, deploy with eve deploy, then install the GitHub App from the Connect dashboard.

FAQ

What happens without GITHUB_ORG set?

The agent has no git__gh tool and cannot open pull requests, though the GitHub channel still answers mentions.

Can I use it only on Slack?

Yes. Delete agent/channels/github.ts, but the agent still needs the GitHub connector and GITHUB_ORG to open pull requests.

What are the requirements?

Node.js 24, pnpm, and the Vercel CLI.