Connect Slack & Deploy Agent

Move the agent beyond the terminal. You will add Slack as a channel, deploy the same agent to Vercel, and continue the conversation with an @mention.

Connect Slack

1. 1

   Add a Slack connector.

   npx eve channels add slack

   Choose the Vercel Connect setup when prompted. Connect manages the Slack bot token, webhook verification, rotation, and workspace tenancy without placing Slack credentials in your source.

2. 2

   Finish the browser setup.

   Select the Slack workspace, approve the requested scopes, and return to the terminal when setup completes.

3. 3

   Deploy when prompted.

   When eve asks Deploy this project to Vercel now?, choose Yes. Save the production URL printed after the deployment. If you choose No, run npx eve deploy before continuing.

4. 4

   Inspect the new channel.

   npx eve channels list npx eve info

   You should see agent/channels/slack.ts and the /eve/v1/slack route.

The built-in Slack channel handles app mentions and direct messages, replies in threads, shows typing state, and renders human-in-the-loop prompts as native buttons or selects.

Verify the deployment

1. 1

   Verify the health route.

   Replace the hostname with the production URL printed during Slack setup:

   curl https://your-agent.vercel.app/eve/v1/health
2. 2

   Connect the terminal to production.

   npx eve dev https://your-agent.vercel.app

   This uses the familiar terminal UI as a client of the deployed agent instead of starting another local server.

3. 3

   Meet the agent in Slack.

   Invite the app to a channel, then send:

   PromptCopy

   @support-agent Triage the sign-in issue for acct_123.

   The reply should land in a thread and use the same instructions and tool as the terminal version.

You are ready when

• eve channels list includes Slack.
• The deployment health route succeeds.
• The remote terminal UI can reach the production URL.
• An app mention in Slack receives a threaded response.