flow

Single application

One app.
Ready to build.

A single-app agentic Next.js template: public Assistant, protected Operator, Eve, OpenUI Lang GenUI, MCP Streamable HTTP, and MCP Apps. Start with a practical baseline and grow only as needed.

Capabilities

A considered starting point.

  • Next.js 16 App Router, React 19, and TypeScript
  • Public Assistant: chat, GenUI playground, and MCP at /api/mcp
  • Protected Operator console and MCP, fail-closed behind OPERATOR_SECRET
  • Eve agent tools, OpenUI Lang GenUI, MCP Streamable HTTP, and MCP Apps
  • Inference through Vercel AI Gateway
  • pnpm qa for lint, types, and tests, plus eval and security-check scripts
  • Flow skills committed in the repository, ready for your agent on clone
  • Vercel-first: every push to main deploys, with no environment variables required

Quick start

From clone to code.

gh repo create my-app --private --template gaboesquivel/flow-next --clonecd my-apppnpm setuppnpm dev

pnpm setup installs dependencies and creates .env.local. Nothing else is required to run it. Open the Portless URL (default host flow-next.localhost).

Prerequisites: Node.js 24+, pnpm 12.14.

Or say “start a Next.js project” and let the start skill set it up.

Why these defaults?

Spend less time on setup.
More time on the product.

The starter supplies engineering conventions and agent-facing capabilities so you can focus on what your application does. Use only the parts you need, and measure deployment time in your own environment.

From the repository README

flow-next README

Rendered at build time from github.com/gaboesquivel/flow-next.

Single-app agentic Next.js template: public Assistant, protected Operator, Eve, OpenUI Lang GenUI, MCP Streamable HTTP, and MCP Apps.

Quick start

bash
gh repo create my-app --private --template gaboesquivel/flow-next --clone
cd my-app
pnpm setup

Then ask your agent to /start (or say "start a new project"): Flow's skills ship in this repository, so it defines the product, renames the template, and makes the initial commit. Run pnpm dev and open the Portless URL (default host flow-next.localhost).

First deployment. Import the repository in Vercel; every push to main deploys. No environment variables are required: without AI_GATEWAY_API_KEY generation falls back to built-in content, and Operator stays closed until OPERATOR_SECRET is set. For a database, run setup with FLOW_PRESET=neon (needs NEON_API_KEY and VERCEL_TOKEN); production builds apply the schema.

Scripts

Script Purpose
pnpm setup Dependencies, .env.local, optional Neon
pnpm dev Development via Portless
pnpm qa Lint, types, tests
pnpm format Format files in place (CI only checks)
pnpm build Production build (includes MCP App bundle)
pnpm eval Offline GenUI eval + Eve tool smoke

Surfaces

  • Assistant — /, /genui, /api/chat, /api/mcp, /mcp
  • Operator — /operator, /api/operator/chat, /api/mcp/operator (requires OPERATOR_SECRET)

Cross-template contract: docs/INTEROP.md.

Eve runtime architecture: docs/agents.md.

Agent skills for this stack: docs/agent-skills.md.

Deploy

Vercel-first; vercel.json runs scripts/vercel-build.mjs (schema on production builds with DATABASE_URL, then pnpm build).

Jump to, or try a question