
Template details
eve TanStack Start Template
Web chat template built on eve and TanStack Start where the agent responds with generative UI such as tables, cards, and dashboards.
About this template
eve TanStack Start Template is a Vercel Labs web chat boilerplate where an eve agent answers with generative UI — result cards, metrics, tables, and dashboards — rendered inside a TanStack Start frontend. Ask it to "Find me the latest Vercel blog posts" and the agent searches the web, then returns a row of cards with a preview image and summary for each post.
What is the eve TanStack Start Template?
It is a starter project pairing an eve agent with a TanStack Start chat app, deployed together on one Vercel project via Vercel Services. The page states the agent lives in agent/ and the chat in apps/web/, and that vercel.ts wraps the chat service in withEve. Input is a natural-language chat message; output is a text answer plus components drawn from a fixed catalog.
Key Features
- Generative UI — the
render_uitool (inrender_ui.ts) outputs result cards, metrics, tables, and other components from a fixed catalog, rendered through json-render. - Interactive prompts — the
ask_questiontool shows selectable options or a typed-answer field so the agent can request input. - Approval flow — the
approval_demotool asks for your approval before it runs. - Web search — the agent searches the web before returning results, e.g. Vercel blog posts as preview cards.
- Password gate — visitors must enter the password set in the
EVE_ACCESS_PASSWORDenvironment variable before chatting. - Persistent, shareable chats — reload the page to return to a conversation, or share its link with anyone holding the password.
- Stack — TanStack Start frontend with TanStack Table for data tables and TanStack Hotkeys for keyboard shortcuts; Vercel Sandbox and Vercel Services for execution and deployment.
- Customization points — persona in
agent/instructions.md, tools inagent/tools/, render catalog inui-catalog.tsandui-registry.tsx, chat UI inapps/web/app/_components/.
How does it work?
Deploying through Vercel's clone flow creates a repository and project, then prompts for EVE_ACCESS_PASSWORD. After deploy, open the URL, enter the password, and send a message that needs a web search. Locally, use Node.js 24 and pnpm, run vercel link and vercel env pull .env.local, then pnpm dev:app to start chat and agent together with vercel dev, routing /eve/v1/* to the agent.
Who is it for?
- Developers prototyping agent chat apps: start from a working eve plus TanStack Start wiring instead of connecting the two from scratch.
- Teams building generative-UI interfaces: use the fixed component catalog and registry to control what the agent can render.
- Anyone wanting a gated internal chat: the shared password keeps a deployment limited to invited people.
Use cases
- Research assistant: ask for the latest blog posts and get web-searched results as card rows with previews and summaries.
- Data reporting: have the agent return tables and metrics rendered by TanStack Table.
- Guided intake: collect answers through the
ask_questionform before continuing a workflow.
















