The Open Framework for Building Agents
Coding Agent on Slack
A coding agent template for eve. Mention it in Slack, or on a GitHub issue or pull request, and it investigates, reviews, or fixes code in an isolated Vercel Sandbox, then answers in the thread or opens a pull request.
How it works
The coding capabilities come from eve's built-in code extension, and GitHub access comes from its companion git extension. This template wires them to Slack and GitHub and keeps everything else default.
agent/
agent.ts model, reasoning, compaction
instructions.md identity and delivery rules
sandbox.ts Vercel Sandbox with gh, git, and TypeScript tooling
extensions/code.ts mounts eve/extensions/code
extensions/git.ts mounts eve/extensions/git with Connect-brokered GitHub access
lib/github.ts Connect connector and the firewall credential broker
hooks/ clears the checkout token before each GitHub turn's model call
channels/slack.ts @mentions in Slack
channels/github.ts @coding-agent comments from trusted repository members
tools/ disables write_file and agent (see below)
- Tools. The code extension adds
code__apply_patchfor edits andcode__grepfor search, next to eve'sbashandread_file. The git extension addsgit__ghfor authenticated GitHub commands.write_fileis disabled so edits go throughcode__apply_patchas small reviewable hunks. - Skills.
code__investigate,code__review, andgit__prload on demand. - Delegation.
code__workeris a read-only subagent for independent slices of a task. The rootagenttool is disabled so all writes stay in one session. - Credentials. Each
ghcommand gets a token scoped to one repository, minted by Vercel Connect. The sandbox only sees a placeholder.lib/github.tsswaps it in at the sandbox firewall for that command and removes it afterward. The GitHub channel's checkout attaches a broader token togithub.com, sohooks/reset-github-egress.tsremoves it before the model runs. - GitHub. The triggering repository is checked out at
/workspacebefore each GitHub turn, and pull request turns include the diff. Only comments from owners, members, and collaborators start a turn, so strangers on a public repository cannot drive the agent.
Getting started
Requires Node.js 24, pnpm, and the Vercel CLI.
pnpm install
vercel link
vercel env pull
pnpm dev
vercel env pull gives the sandbox and AI Gateway their credentials. The dev UI opens a session with the agent. Without GITHUB_ORG the agent has no git__gh tool and can't open pull requests. The GitHub channel still answers mentions.
Connect Slack and GitHub
Slack. Run eve add channel/slack. It creates or picks a Slack app through Vercel Connect, routes its events to /eve/v1/slack, and writes the connector UID into agent/channels/slack.ts.
GitHub. Don't use eve add channel/github here. It stops with an error because agent/channels/github.ts already exists, and --overwrite replaces the file along with its rule that only repository owners, members, and collaborators can start a turn. Create the connector with the Vercel CLI instead:
vercel connect create github --name coding-agent --triggers \
--trigger-event issue_comment --trigger-event pull_request_review_comment
vercel connect detach github/coding-agent --yes
vercel connect attach github/coding-agent --environment production \
--triggers --trigger-path /eve/v1/github --yes
These are the commands eve add channel/github runs. create adds a default webhook destination without a path, so detach removes it before attach routes webhooks to /eve/v1/github.
Then set these in .env.local and your Vercel project:
GITHUB_ORG: the organization or user whose repositories the agent may accessGITHUB_CONNECTOR: the connector UID, if it is notgithub/coding-agentGITHUB_BOT_NAME: your GitHub App's slug, shown on the connector in the Connect dashboard
Deploy with eve deploy, then install the GitHub App on your repositories from the Connect dashboard. Mention the app in Slack, or comment @<bot name> <request> on an issue or pull request. Delete agent/channels/github.ts if you only want Slack; the agent still needs the GitHub connector and GITHUB_ORG to open pull requests.
Customize
- Change the model in
agent/agent.ts. - Edit
agent/instructions.mdfor tone and team conventions. The extensions add their own coding guidance, so keep this file short. - Add skills under
agent/skills/, tools underagent/tools/, or override an extension contribution by name. See Extensions. - The default HTTP channel accepts the eve TUI, Vercel OIDC, and local development. Add
agent/channels/eve.tsto put your own auth in front of it. See Auth and route protection.