eve Slack Company Brain Template

The eve Slack Company Brain Template is an open-source starter for a company-wide Slack assistant, built on the eve agent framework and deployed on Vercel. People mention the agent in a channel or DM it, and it answers in a thread using sources you connect, with inline links and explicit gaps when nothing answers the question.

What is the Slack Company Brain Template?

The Slack Company Brain Template is a starting point for a company-wide assistant in Slack, built with the eve agent framework and shipped as an app template in the vercel/eve repository. It takes company knowledge from connectors such as Notion, Linear, and PagerDuty plus Slack channel history, and produces threaded Slack answers, private and per-channel memory, and scheduled task results posted back to the conversation where they were created. Out of the box it knows nothing about your company; you grow it by adding sources, procedures, and specialists.

Key Features

• Grounded answers — the instructions require the agent to answer company-specific questions only from retrieved sources, link the source inline, and say when nothing answers the question.
• Thread context — each mention sees the replies posted since the agent last spoke, with sender names.
• Followed threads — once brought into a thread, the agent sees later replies without a mention and calls no_reply when a reply isn't meant for it; this needs the message.channels event and channels:history scope.
• Slack search — search_slack calls Slack's Real-time Search API via assistant.search.context, searching public channels only, citing permalinks; read_slack_conversation reads a matched thread or named channel.
• Workspace gate — Slack guests and deactivated accounts cannot start conversations or answer approvals, and SLACK_TEAM_ID blocks people from other companies in Slack Connect channels.
• Two memory slots — a private per-person slot (DMs and non-Slack channels) and a shared per-channel slot, stored in a private Vercel Blob store.
• Scheduled tasks — built on eve's experimental dynamic schedules, giving create, list, update, and delete tools so people manage recurring or one-time work by asking in Slack; each run executes as the schedule's creator.
• Code and GitHub — the eve code extension runs scripts and analyzes attached files such as CSVs in a Vercel Sandbox, and the git extension adds a git__gh tool plus a pr skill for draft pull requests; GitHub tokens are swapped in at the sandbox firewall.

Who is it for?

• Platform or IT teams standing up an internal assistant: deploy the template, fill in agent/skills/company-context/SKILL.md with teams, glossary, and sources, and connect Notion, Linear, or PagerDuty connectors named company-brain.
• Engineering organizations: use the git extension so the agent reads repositories, issues, and pull requests and opens draft PRs, with GitHub App tokens scoped to one repository per command.
• Teams that want recurring Slack summaries: ask the agent to post a digest every weekday at 9am in a channel; results land where the schedule was created and run as the creator.

Use cases

• On-call and incident lookup: connect PagerDuty to answer questions about on-call schedules, incidents, and services, using your own PagerDuty OAuth app registered under Developer Tools > App Registration.
• Wiki and project questions: connect Notion for page search and Linear for issues, projects, and cycles, keeping the connection read-only by limiting allowed tools such as notion-search and notion-fetch.
• File analysis in Slack: attach a CSV or log and have the agent run code in its sandbox to analyze it.
• Reminders in threads: ask for a reminder in a thread in two hours and the schedule replies to that thread.

How does the Slack Company Brain Template work?

Install with pnpm, link a Vercel project, run vercel connect create slack with a trigger path of /eve/v1/slack to create the Slack app, set SLACK_CONNECTOR and SLACK_TEAM_ID, run eve integration setup file-memory for the Blob store, then eve deploy. The agent picks up new connectors within a few minutes without a redeploy, and each source's instructions file under agent/instructions/ should be deleted once that connector works.

FAQ

Is the Slack Company Brain Template free?

The template is source code published in the vercel/eve open repository, so the template itself carries no listed price. Running it depends on your own Vercel project, AI Gateway access, and Slack app, and memory on Vercel requires a private Vercel Blob store created by eve integration setup file-memory or the Deploy with Vercel button.

Does Slack search work everywhere?

No. search_slack relies on the short-lived action_token from the message that started the turn, so it works only in turns started by a mention or DM. It fails in scheduled tasks, followed-thread replies without a mention, and non-Slack channels, and the tool reports the gap instead of claiming nothing was found.

What is the default memory behavior?

There are two file-memory slots. Personal memory is off in shared conversations including group DMs, and channel memory is off in DMs; scopes come from the trusted Slack session in lib/conversation.ts, never from the model. Under eve dev, memory lives in process memory and resets on restart.

Can the sandbox reach any host?

Yes. The sandbox has open egress, so code the agent runs can reach any host; only GitHub credentials are held back at the firewall. The documentation advises against putting other credentials in the sandbox and suggests narrowing the network policy in agent/sandbox.ts and lib/github.ts.