mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
08d94575c2
Restructure /threads using TailoredContent so users pick between bootstrapping a new project with the v-next CLI or wiring threads into an existing CopilotKit app. The CLI path walks through `npx -y @copilotkit/cli-vnext@latest create`, enabling Intelligence when prompted, cd-ing into the project, installing deps, adding the OpenAI key, and `npm run dev` (which boots the local Intelligence Platform, BFF, and web app at localhost:3000). The manual path preserves the original 4-step flow (runtime config, useThreads, thread switching, pagination). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fumadocs-test
This is a Next.js application generated with Create Fumadocs.
Run development server:
npm run dev
# or
pnpm dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
Learn More
To learn more about Next.js and Fumadocs, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
- Fumadocs - learn about Fumadocs
Vercel Deployment with Git LFS
Docs assets are tracked with Git LFS. To ensure production builds always receive
real asset bytes (not pointer files), deploy docs through GitHub Actions using
.github/workflows/deploy_docs_vercel.yml.
Required GitHub repository secrets:
VERCEL_TOKENVERCEL_ORG_IDVERCEL_PROJECT_ID_DOCS
PR previews:
.github/workflows/deploy_docs_vercel_preview.ymldeploys docs previews for non-fork pull requests.- The workflow posts/updates a sticky PR comment with a clickable
Open Docs Previewlink.
Recommended Vercel project setting:
- Disable automatic Git-based deployments for the docs project and let the GitHub Actions workflow handle production deploys.