Root cause of the parity-check CI failures:
The 5 verbatim-tracked files in `examples/integrations/langgraph-python/`
(the north-star) all carried `typescript/consistent-type-imports` and
`react/self-closing-comp` warnings that oxlint wants to auto-fix.
The lefthook pre-commit `lint-fix` hook is scoped to staged files
and re-stages fixes via `stage_fixed: true`. So when I ran
`pnpm parity:sync --target=strands-python` and staged the synced
files, oxlint --fix rewrote them on commit to satisfy the
type-imports rule — turning `import { NextRequest }` into
`import type { NextRequest }`, etc. The north-star was never touched
by the hook (nothing staged in langgraph-python/), so it kept the
un-fixed form. The two diverged at commit time and parity:check
caught the drift.
Two prior commits (0559faf3d, 80425fcc8) tried to land the sync but
each landed empty: lefthook + stage_fixed reverted the working-tree
changes to match the north-star's un-fixed form, then the linter's
auto-fix re-applied the same delta the hook had just undone — net
zero file content but with the linter-fixed form, which the post-
commit hook then reverted again. Hard to debug because `git
commit` reported success and shortstat hid the no-op.
This commit fixes the root cause instead of the symptom:
1. Apply `pnpm exec oxlint --fix` directly to the 5 north-star
files (`docker-route-override.ts`,
`src/app/declarative-generative-ui/renderers.tsx`,
`src/components/ui/{badge,button}.tsx`, `src/lib/utils.ts`).
The fixes match what the pre-commit hook would have applied:
type-only imports → `import type`, self-closing JSX → `<X />`.
2. Re-run `pnpm parity:sync` for all three instances
(strands-python, langgraph-fastapi, langgraph-js) so they
verbatim-match the new north-star.
3. Verified `pnpm parity:check` exits 0; all four trees lint clean
(`pnpm exec oxlint examples/integrations/.../`).
Net effect: every instance now matches the north-star byte-for-byte,
and the lint-fix hook is a no-op on these files going forward.
Files touched per directory (5 each, except strands-python which had
docker-route-override.ts already synced in a prior attempt):
examples/integrations/langgraph-python/ — 5 files
examples/integrations/langgraph-fastapi/ — 5 files
examples/integrations/langgraph-js/ — 5 files
examples/integrations/strands-python/ — 4 files
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CopilotKit <> LangGraph Starter
This is a starter template for building AI agents using LangGraph and CopilotKit. It provides a modern Next.js application with an integrated LangGraph agent to be built on top of.
https://github.com/user-attachments/assets/47761912-d46a-4fb3-b9bd-cb41ddd02e34
Prerequisites
- Node.js 18+
- Python 3.12+
- uv (Python package manager)
- Any of the following package managers:
- OpenAI API Key (for the LangGraph agent)
Getting Started
- Install dependencies using your preferred package manager:
# Using npm (default)
npm install
# Using pnpm
pnpm install
# Using yarn
yarn install
# Using bun
bun install
This will also install the Python agent dependencies via uv sync.
- Set up your environment variables:
cp .env.example .env
Then edit the .env file and add your OpenAI API key:
OPENAI_API_KEY=your-openai-api-key-here
- Start the development server:
# Using npm (default)
npm run dev
# Using pnpm
pnpm dev
# Using yarn
yarn dev
# Using bun
bun run dev
This will start both the UI and agent servers concurrently.
Available Scripts
The following scripts can also be run using your preferred package manager:
dev- Starts both UI and agent servers in development modedev:debug- Starts development servers with debug logging enableddev:ui- Starts only the Next.js UI serverdev:agent- Starts only the LangGraph agent serverbuild- Builds the Next.js application for productionstart- Starts the production serverinstall:agent- Installs Python dependencies for the agent
Project Structure
├── src/ # Next.js frontend source
│ ├── app/
│ │ ├── page.tsx # Main page
│ │ └── api/copilotkit/ # CopilotKit API route
│ ├── components/
│ │ ├── example-canvas/ # Todo list UI
│ │ ├── example-layout/ # Layout: chat + canvas side-by-side
│ │ └── generative-ui/ # Example generative UI components
│ └── hooks/
├── agent/ # LangGraph Python agent
│ ├── main.py # Agent entry point
│ └── src/
│ ├── todos.py # Todo tools and state schema
│ └── query.py # Example data query tool
├── scripts/ # Agent setup and run scripts
│ ├── setup-agent.sh / .bat
│ └── run-agent.sh / .bat
├── public/ # Static assets
├── next.config.ts
├── tsconfig.json
└── package.json
A2UI — Agent-to-User Interface
This starter includes A2UI support, allowing the agent to generate rich, interactive UI surfaces declaratively. Instead of returning plain text, the agent sends a JSON description of the UI it wants to render, and the frontend turns it into real components.
How it works
A2UI uses three concepts:
- Catalog — a set of component definitions (schema) paired with React renderers. Registered once in
layout.tsxvia<CopilotKitProvider a2ui={{ catalog: demonstrationCatalog }}>. - Surface — a rendered UI instance. The agent creates a surface, sets its components, and binds data to it.
- Operations — the agent returns
a2ui.render(operations=[...])from a tool, which the middleware streams to the frontend.
Two patterns
| Pattern | Description | Agent tool | Frontend |
|---|---|---|---|
| Fixed schema | Pre-defined component layout. Only the data changes per invocation. | search_flights |
Schema in a2ui/schemas/flight_schema.json |
| Dynamic schema | A secondary LLM generates both components and data based on the conversation. | generate_a2ui |
Components decided at runtime |
Both patterns use the same catalog on the frontend — the difference is where the component tree comes from.
Key files
| Purpose | Path |
|---|---|
| Catalog definitions (Zod schemas) | src/app/declarative-generative-ui/definitions.ts |
| Catalog renderers (React components) | src/app/declarative-generative-ui/renderers.tsx |
| Catalog registration | src/app/layout.tsx |
| Fixed-schema agent tool | agent/src/a2ui_fixed_schema.py |
| Dynamic-schema agent tool | agent/src/a2ui_dynamic_schema.py |
| Flight schema JSON | agent/src/a2ui/schemas/flight_schema.json |
| Showcase config | showcase.json |
Adding a custom component
-
Define the component schema in
definitions.ts:MyWidget: { description: "A brief description for the agent.", props: z.object({ title: z.string(), value: z.number() }), }, -
Render it in
renderers.tsx:MyWidget: ({ props }) => ( <div>{props.title}: {props.value}</div> ),Renderers are type-checked against the definitions — TypeScript will error if props don't match.
-
Use it from the agent. The component is automatically available to both fixed-schema templates and the dynamic-schema LLM.
Adding a new fixed-schema tool
- Create a JSON schema file in
agent/src/a2ui/schemas/describing the component tree. - Create a Python tool that loads the schema with
a2ui.load_schema()and returnsa2ui.render(operations=[...])with your data. Seea2ui_fixed_schema.pyfor the pattern.
Showcase mode
showcase.json controls which suggestion pills are visually highlighted. Set "showcase": "a2ui" to highlight the A2UI demos, or "showcase": "default" for no highlights. This is configured automatically when scaffolding via npx copilotkit create --framework a2ui.
Further reading
Documentation
- LangGraph Documentation - Learn more about LangGraph and its features
- CopilotKit Documentation - Explore CopilotKit's capabilities
Contributing
Feel free to submit issues and enhancement requests! This starter is designed to be easily extensible.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Troubleshooting
Agent Connection Issues
If you see "I'm having trouble connecting to my tools", make sure:
- The LangGraph agent is running on port 8123
- Your OpenAI API key is set correctly
- Both servers started successfully
Python Dependencies
If you encounter Python import errors:
npm run install:agent