AgentFast docs

AgentFast is a builder-first Next.js starter kit for shipping AI products with the production layer already wired. Instead of starting from a prompt demo and rebuilding auth, billing, embeds, logs, and deployment later, you start from a codebase that already handles those pieces.

• Auth and database wiring with Supabase
• Embeddable chat, API access, and webhook execution
• Run logs, analytics, and cost guardrails
• Starter templates for chat, research, and ops workflows

Purchase unlocks the starter kit so you can clone, configure, and ship your own product quickly. The point is immediate execution, not access to a waitlist.

• Full Next.js codebase and starter templates
• Auth, billing, embeds, logs, and guardrails already wired
• Private repo invite sent to the GitHub username you submit after checkout
• Setup documentation and launch-ready defaults
• Current launch update window and direct founder support

The local setup path is intentionally short. Configure the env file, apply the schema, and start customizing.

Minimum local boot needs NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, and AI_GATEWAY_API_KEY. Stripe, search, Slack, MCP, and embed secrets are optional and only enable related features.

git clone <private-repo-url> my-agent
cd my-agent
npm install
cp .env.example .env.local
# Recommended on a fresh project:
# paste supabase/setup.sql into Supabase SQL Editor
# CLI alternative, after supabase login + supabase link:
# supabase db push
npm run dev

After repo access is granted, use the private clone URL from GitHub, start the app locally, sign up with email/password, create an agent from a template, and run a dashboard test before you start changing product logic. GitHub is only used for repo invite/access, not for app auth.

Supabase is the default foundation for auth, data, and protected app state.

• Create a Supabase project and copy the project URL and anon key.
• Add NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, and SUPABASE_SERVICE_ROLE_KEY to your env file.
• For the simplest manual setup, open supabase/setup.sql, paste it into the Supabase SQL Editor, and run it once on a new project.
• If you prefer the CLI workflow, run supabase login, supabase link, then supabase db push. It applies the same schema from the ordered files in supabase/migrations.
• Set your local and production site URLs in Supabase auth so email confirmation and redirects work correctly.

Stripe is optional until you want billing in your own product, but the starter kit already includes checkout hooks and plan wiring.

STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...
STRIPE_WEBHOOK_ENDPOINT_URL=https://your-domain.com/api/webhooks/stripe
STRIPE_STARTER_PRICE_ID=price_...
STRIPE_PRO_PRICE_ID=price_...

If you want a faster starting point, provision the initial products and prices with npm run stripe:provision, then copy the generated price IDs into your env file.

The quickest production path is Vercel for the app plus Supabase for data.

• Import the repo into Vercel and add the same env vars you use locally.
• Set NEXT_PUBLIC_APP_URL to your production domain.
• Point your Stripe webhook endpoint at /api/webhooks/stripe on the deployed domain.
• Check /api/health right after deploy.
• Redeploy after env changes, then confirm auth, checkout, and agent runs from a real browser session.

AgentFast is built to be modified with Claude, Codex, Cursor, and similar coding agents, but the handoff works best when you give the agent the right files first.

• CLAUDE.md for the repo map and task router
• README.md for setup order and first-success flow
• .env.example for the runtime env contract
• supabase/setup.sql for the fresh-project schema
• Tell the agent which surface matters first: dashboard, embed, API, or webhook

Good prompt shape: the product surface, the exact user flow, and whether billing, embeds, or webhooks need to be live on day one.

AgentFast is strongest when you start from an opinionated template and then narrow it into your product.