Convex Quickstart

Set up a working Convex project as fast as possible.

When to Use

• Starting a brand new project with Convex
• Adding Convex to an existing React, Next.js, Vue, Svelte, or other app
• Scaffolding a Convex app for prototyping

When Not to Use

• The project already has Convex installed and convex/ exists - just start building
• You only need to add auth to an existing Convex app - use the convex-setup-auth skill

Workflow

1. Determine the starting point: new project or existing app
2. If new project, pick a template and scaffold with npm create convex@latest
3. If existing app, install convex and wire up the provider
4. Run npx convex dev to connect a deployment and start the dev loop
5. Verify the setup works

Path 1: New Project (Recommended)

Use the official scaffolding tool. It creates a complete project with the frontend framework, Convex backend, and all config wired together.

Pick a template

If the user has not specified a preference, default to react-vite-shadcn for simple apps or nextjs-shadcn for apps that need SSR or API routes.

You can also use any GitHub repo as a template:

bash
1npm create convex@latest my-app -- -t owner/repo
2npm create convex@latest my-app -- -t owner/repo#branch

Scaffold the project

Always pass the project name and template flag to avoid interactive prompts:

bash
1npm create convex@latest my-app -- -t react-vite-shadcn
2cd my-app
3npm install

The scaffolding tool creates files but does not run npm install, so you must run it yourself.

To scaffold in the current directory (if it is empty):

bash
1npm create convex@latest . -- -t react-vite-shadcn
2npm install

Start the dev loop

npx convex dev is a long-running watcher process that syncs backend code to a Convex deployment on every save. It also requires authentication on first run (browser-based OAuth). Both of these make it unsuitable for an agent to run directly.

Ask the user to run this themselves:

Tell the user to run npx convex dev in their terminal. On first run it will prompt them to log in or develop anonymously. Once running, it will:

• Create a Convex project and dev deployment
• Write the deployment URL to .env.local
• Create the convex/ directory with generated types
• Watch for changes and sync continuously

The user should keep npx convex dev running in the background while you work on code. The watcher will automatically pick up any files you create or edit in convex/.

Exception - cloud or headless agents: Environments that cannot open a browser for interactive login should use Agent Mode (see below) to run anonymously without user interaction.

Start the frontend

The user should also run the frontend dev server in a separate terminal:

bash
1npm run dev

Vite apps serve on http://localhost:5173, Next.js on http://localhost:3000.

What you get

After scaffolding, the project structure looks like:

my-app/
  convex/           # Backend functions and schema
    _generated/     # Auto-generated types (check this into git)
    schema.ts       # Database schema (if template includes one)
  src/              # Frontend code (or app/ for Next.js)
  package.json
  .env.local        # CONVEX_URL / VITE_CONVEX_URL / NEXT_PUBLIC_CONVEX_URL

The template already has:

• ConvexProvider wired into the app root
• Correct env var names for the framework
• Tailwind and shadcn/ui ready (for shadcn templates)
• Auth provider configured (for auth templates)

Proceed to adding schema, functions, and UI.

Path 2: Add Convex to an Existing App

Use this when the user already has a frontend project and wants to add Convex as the backend.

Install

bash
1npm install convex

Initialize and start dev loop

Ask the user to run npx convex dev in their terminal. This handles login, creates the convex/ directory, writes the deployment URL to .env.local, and starts the file watcher. See the notes in Path 1 about why the agent should not run this directly.

Wire up the provider

The Convex client must wrap the app at the root. The setup varies by framework.

Create the ConvexReactClient at module scope, not inside a component:

tsx
1// Bad: re-creates the client on every render
2function App() {
3  const convex = new ConvexReactClient(
4    import.meta.env.VITE_CONVEX_URL as string,
5  )
6  return <ConvexProvider client={convex}>...</ConvexProvider>
7}
8
9// Good: created once at module scope
10const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string)
11function App() {
12  return <ConvexProvider client={convex}>...</ConvexProvider>
13}

React (Vite)

tsx
1// src/main.tsx
2import { ConvexProvider, ConvexReactClient } from "convex/react"
3import { StrictMode } from "react"
4import { createRoot } from "react-dom/client"
5import App from "./App"
6
7const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string)
8
9createRoot(document.getElementById("root")!).render(
10  <StrictMode>
11    <ConvexProvider client={convex}>
12      <App />
13    </ConvexProvider>
14  </StrictMode>,
15)

Next.js (App Router)

tsx
1// app/ConvexClientProvider.tsx
2"use client"
3
4import { ConvexProvider, ConvexReactClient } from "convex/react"
5import { ReactNode } from "react"
6
7const convex = new ConvexReactClient(process.env.NEXT_PUBLIC_CONVEX_URL!)
8
9export function ConvexClientProvider({ children }: { children: ReactNode }) {
10  return <ConvexProvider client={convex}>{children}</ConvexProvider>
11}

tsx
1// app/layout.tsx
2import { ConvexClientProvider } from "./ConvexClientProvider"
3
4export default function RootLayout({
5  children,
6}: {
7  children: React.ReactNode
8}) {
9  return (
10    <html lang="en">
11      <body>
12        <ConvexClientProvider>{children}</ConvexClientProvider>
13      </body>
14    </html>
15  )
16}

Other frameworks

For Vue, Svelte, React Native, TanStack Start, Remix, and others, follow the matching quickstart guide:

• Vue
• Svelte
• React Native
• TanStack Start
• Remix
• Node.js (no frontend)

Environment variables

The env var name depends on the framework:

npx convex dev writes the correct variable to .env.local automatically.

Agent Mode (Cloud and Headless Agents)

When running in a cloud or headless agent environment where interactive browser login is not possible, set CONVEX_AGENT_MODE=anonymous to use a local anonymous deployment.

Add CONVEX_AGENT_MODE=anonymous to .env.local, or set it inline:

bash
1CONVEX_AGENT_MODE=anonymous npx convex dev

This runs a local Convex backend on the VM without requiring authentication, and avoids conflicting with the user's personal dev deployment.

Verify the Setup

After setup, confirm everything is working:

1. The user confirms npx convex dev is running without errors
2. The convex/_generated/ directory exists and has api.ts and server.ts
3. .env.local contains the deployment URL

Writing Your First Function

Once the project is set up, create a schema and a query to verify the full loop works.

convex/schema.ts:

ts
1import { defineSchema, defineTable } from "convex/server"
2import { v } from "convex/values"
3
4export default defineSchema({
5  tasks: defineTable({
6    text: v.string(),
7    completed: v.boolean(),
8  }),
9})

convex/tasks.ts:

ts
1import { v } from "convex/values"
2import { mutation, query } from "./_generated/server"
3
4export const list = query({
5  args: {},
6  handler: async (ctx) => {
7    return await ctx.db.query("tasks").collect()
8  },
9})
10
11export const create = mutation({
12  args: { text: v.string() },
13  handler: async (ctx, args) => {
14    await ctx.db.insert("tasks", { text: args.text, completed: false })
15  },
16})

Use in a React component (adjust the import path based on your file location relative to convex/):

tsx
1import { useMutation, useQuery } from "convex/react"
2import { api } from "../convex/_generated/api"
3
4function Tasks() {
5  const tasks = useQuery(api.tasks.list)
6  const create = useMutation(api.tasks.create)
7
8  return (
9    <div>
10      <button onClick={() => create({ text: "New task" })}>Add</button>
11      {tasks?.map((t) => (
12        <div key={t._id}>{t.text}</div>
13      ))}
14    </div>
15  )
16}

Development vs Production

Always use npx convex dev during development. It runs against your personal dev deployment and syncs code on save.

When ready to ship, deploy to production:

bash
1npx convex deploy

This pushes to the production deployment, which is separate from dev. Do not use deploy during development.

Next Steps

• Add authentication: use the convex-setup-auth skill
• Design your schema: see Schema docs
• Build components: use the convex-create-component skill
• Plan a migration: use the convex-migration-helper skill
• Add file storage: see File Storage docs
• Set up cron jobs: see Scheduling docs

Checklist

• Determined starting point: new project or existing app
• If new project: scaffolded with npm create convex@latest using appropriate template
• If existing app: installed convex and wired up the provider
• User has npx convex dev running and connected to a deployment
• convex/_generated/ directory exists with types
• .env.local has the deployment URL
• Verified a basic query/mutation round-trip works