A persisted Next.js chat template for eve, built with shadcn/ui, Tailwind CSS, Streamdown, Better Auth, Drizzle, Neon, and Upstash Redis.

Two ways to get going:

• One-click: use the Deploy with Vercel button above to clone and provision storage, then run migrations (see Setup and Deployment).
• Local script: clone the repo and run the setup script. It links the project, provisions Neon, registers the Sign in with Vercel OAuth app (email scope + callbacks), sets the environment variables through the Vercel API, pulls them locally, runs migrations, and can optionally set up the Notion connector. If OAuth app registration isn't available it falls back to a guided manual flow.

# Uses the linked project's team by default
./scripts/setup.sh

# Or target a specific team (also accepts a bare team slug)
./scripts/setup.sh --scope <team-slug>

The --scope is optional; omit it to use the linked project's team. The script needs the vercel CLI, node, pnpm, and openssl. Prefer to do it by hand? Follow the sequential steps below, or the full Setup and Deployment guide.

For the full local setup, storage provisioning, Sign in with Vercel credentials, and production deploy flow, see Setup and Deployment. For the runtime architecture, streaming model, persistence flow, and extension points, see How the Chatbot Works.

Install dependencies with pnpm:

pnpm install

Link the Vercel project and pull environment variables:

vercel link

Provision storage with the Vercel CLI integration commands:

# Required: persisted chat, auth, eve session state, and message snapshots
vercel integration add neon

# Required: Redis-backed rate limiting
vercel integration add upstash

Follow the prompts to connect each resource to the linked project. Then pull the generated environment variables locally:

vercel env pull .env.local --yes

Required environment variables:

DATABASE_URL=
BETTER_AUTH_SECRET=
NEXT_PUBLIC_VERCEL_APP_CLIENT_ID=
VERCEL_APP_CLIENT_SECRET=
UPSTASH_REDIS_REST_URL=
UPSTASH_REDIS_REST_TOKEN=
KV_REST_API_URL=
KV_REST_API_TOKEN=

Optional environment variables:

# Override the app origin for custom production domains.
BETTER_AUTH_URL=

# Enable hosted Vercel Connect integrations.
SLACK_CONNECTOR=
LINEAR_CONNECTOR=
NOTION_CONNECTOR=
SENTRY_CONNECTOR=

Create optional Vercel Connect integrations:

# Slack channel
vercel connect create slack --name eve-chat-template --triggers
vercel connect attach <slack-connector-uid> --triggers --trigger-path /eve/v1/slack --yes

# MCP connections
vercel connect create mcp.notion.com --name notion
vercel connect create https://mcp.linear.app/mcp --name linear
vercel connect create https://mcp.sentry.dev/mcp --name sentry

The deploy button does not require these integrations. For manual setup, put the returned connector UIDs in SLACK_CONNECTOR, NOTION_CONNECTOR, LINEAR_CONNECTOR, and SENTRY_CONNECTOR. Local development falls back to slack/eve-chat-template, notion, linear, and sentry, so connectors created with the names above work without editing agent/.

If the connector is not attached to the linked project, run:

vercel connect attach <connector-uid> --yes
vercel env pull .env.local

Create the database tables:

pnpm db:migrate

For production, run migrations with Vercel production env vars:

vercel env run -e production -- pnpm db:migrate

Start the development server:

pnpm dev

• Text chat with an eve agent through same-origin /eve/v1/* routes
• Better Auth sign-in with Vercel
• Mandatory Neon-backed chat history
• Mandatory Upstash Redis rate limiting for authenticated chat sends
• Drizzle schema and migrations under lib/db
• Saved eve session cursors and event snapshots
• Sidebar history with delete and new-chat actions
• Vercel Connect-backed Notion, Linear, and Sentry MCP connections
• Vercel Connect-backed Slack channel route at /eve/v1/slack
• Composer-level connections menu
• First-message chat titles derived locally from the user's prompt
• Streamdown markdown rendering for assistant text and reasoning
• shadcn/Tailwind components for messages, tools, HITL prompts, and composer

This template intentionally does not include file uploads, Vercel Blob, guest mode, NextAuth/Auth.js, or AI Elements.

Edit the agent in agent/agent.ts. Its behavior is defined in agent/instructions.md, and tools live in agent/tools/.

The browser talks to eve with useEveAgent() from eve/react; the app stores eve stream events and session state so /chat/[id] can resume the same durable conversation after refresh.