flow

Multi-package application

One repo.
Room to grow.

A minimal Turborepo template for agent-first Next.js apps: public Assistant (chat, MCP, OpenUI GenUI) and protected Operator diagnostics, with shared UI in its own package.

Capabilities

A considered starting point.

  • Turborepo with apps/web (Next.js 16, React 19) and packages/ui
  • Shared shadcn base-nova components and tokens in packages/ui
  • 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
  • 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: set apps/web as the project root; its vercel.json builds the workspace

Quick start

From clone to code.

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

pnpm setup installs dependencies and creates the .env.local files. Open the Portless URL (typically app.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-mono README

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

Minimal Turborepo template for agent-first Next.js apps: public Assistant (chat, MCP, OpenUI GenUI) and protected Operator diagnostics.

Prerequisites

  • Node.js 24+
  • pnpm 12.14 (see packageManager in package.json)

Quick start

bash
gh repo create my-app --private --template gaboesquivel/flow-mono --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 (typically app.localhost).

First deployment. Import the repository in Vercel with apps/web as the root directory; 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 files, optional Neon
pnpm setup:portless Trust Portless proxy
pnpm dev Dev server via Portless
pnpm dev:app Next.js only
pnpm qa Lint, types, tests
pnpm format Format files in place (CI only checks)
pnpm build Production build
pnpm eval Offline GenUI matrix + Eve smoke evals

Structure

  • apps/web — Next.js app, MCP, GenUI, Eve agent tools
  • packages/ui — shadcn base-nova components and tokens

Operator access

Set OPERATOR_SECRET in the environment (minimum 16 characters). Call protected routes with Authorization: Bearer <secret> or X-Operator-Secret, or use /operator/access for the web console. Without configuration, operator surfaces fail closed.

  • Assistant — /, /genui, /api/chat, /api/mcp, /mcp
  • Operator — /operator, /api/operator/chat, /api/mcp/operator

Cross-template contract: docs/INTEROP.md.

Eve runtime architecture: docs/agents.md.

Agent skills: docs/agent-skills.md.

Deploy

Vercel-first; the project root is apps/web, whose vercel.json installs from the workspace root and runs scripts/vercel-build.mjs (schema on production builds with DATABASE_URL, then the web build).

Jump to, or try a question