AI Slackbot

ai-slackbot

Vercel's AI SDK Slackbot template — an AI chatbot for Slack that answers app mentions and direct messages with an LLM and tools (weather, dice, a sandboxed bash, web search), every tool call gated by an Open Policy Agent policy compiled to WebAssembly — running natively as a Cloudflare Worker, and packaged as an Orun baseline: one command takes a new Slack bot from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing.

Upstream's api/events.ts (a Vercel function) is a Hono route here, at the same path: Hono's fetch handler is the Worker's, no adapter. It verifies Slack's signature with WebCrypto before anything else, acknowledges at once and answers in waitUntil. The model is Workers AI through the Worker's own AI binding, so a fresh bot needs no AI key; upstream's OpenAI is used, directly, once its key is stored. The policy, the agent loop and the tools are upstream's. The bot is born not connected: it deploys and /api/events says so until its owner creates a Slack app and stores its two keys. What the baseline adds is everything needed to make a copy of it somebody else's — built the way cirrus-baseline is. See specs/epics/ai-slackbot for the design, the milestones and the as-built status.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/ai-slackbot
cd ai-slackbot
orun new --blueprint repo-blueprint.yaml --out ~/bots/acme-assistant --run-hooks --resume \
  --set reponame=acme-assistant --set productname="Acme Assistant" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → ai-slackbot → Build). Two phases — 01-product (the repository, its CI and the whole bot in one pull request, deployed to stage and prod by one convergence, smoke-tested) and 02-docs (the live deployment recorded) — each landing one pull request in the new repository. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

The new repository receives the bot only — the Worker, its policy, its tests, its CI, its tooling, a README of its own, its operating contract and the template's licence — renamed throughout to the bot's name, repository and Cloudflare Worker. None of this repository's machinery ships, and nothing that ships names it.

What is here (the product)

Getting started

pnpm install
pnpm typecheck
pnpm lint
pnpm test
pnpm build            # wrangler deploy --dry-run → apps/api/dist (the bundle, no upload)

Run the Worker locally under workerd (Workers AI has no local mode, so wrangler dev needs wrangler login; Slack's two keys go in apps/api/.dev.vars):

pnpm --filter @app/api dev        # http://localhost:8787
curl http://localhost:8787/health # {"status":"ok","name":"AI SDK Slackbot","environment":"local","slack":…}

The product README (.baseline/product/README.md) says how to create the Slack app and connect it.

How it maps to Vercel

CI

Credits

The bot is Vercel's AI SDK Slackbot template (vercel-labs/ai-sdk-slackbot, MIT as its README declares; the repository has no LICENSE file — apps/api/LICENSE.md).