CopilotKit <> Agno Starter
This is a starter template for building AI agents using Agno and CopilotKit. It provides a modern Next.js application with an integrated investment analyst agent that can research stocks, analyze market data, and provide investment insights.
Prerequisites
- Node.js 20+
- Python 3.12+
- uv (Python package manager)
- OpenAI API Key (for the Agno agent)
- Any of the following package managers:
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
Note: Installing the package dependencies will also install the agent's python dependencies via the
install:agentscript.
- Set up your OpenAI API key:
export OPENAI_API_KEY="your-openai-api-key-here"
or create a .env file.
echo "OPENAI_API_KEY=your-openai-api-key-here" > .env
- 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.
Running a Channel
channel-host.mts mounts the same agent as an Intelligence Channel
(Slack, Teams). It requires CPK_INTELLIGENCE_API_KEY and a declared Channel in
.copilotkit/channels.json — set both up with copilotkit init or
copilotkit channels add, which write that file and the credentials your
.env needs, then:
npm run channel
The host reads which Channel to hold from .copilotkit/channels.json. If a
project declares more than one, set INTELLIGENCE_CHANNEL_NAME to pick one.
The host holds no provider credentials and exposes no provider endpoint — Intelligence owns the provider edge — so the same file works for every provider.
The Channel itself is declared in channels.mts — that is where to add commands,
reactions, or an onMention handler. channel-host.mts only owns the process
lifetime, and is byte-identical in every starter.
Once startup finishes, the log reports the truth per Channel:
Channel "<name>" is online.— the session is up and can send.Channel "<name>" is declared but no provider is attached yet.— a normal waiting state, not a failure. Runcopilotkit channels statusto see what setup remains.
Neither message proves the provider app is installed, reachable, or that anyone can message it — verify that separately (invite the bot, then message it) before treating the Channel as working.
Available Scripts
The following scripts can also be run using your preferred package manager:
dev- Starts both UI and agent servers in development modedev:ui- Starts only the Next.js UI serverdev:agent- Starts only the Agno agent serverbuild- Builds the Next.js application for productionstart- Starts the production serverinstall:agent- Installs Python dependencies for the agentchannel- Holds an Intelligence Channel open (see "Running a Channel" above)typecheck:channel- Type-checks the channel host on its owntsconfig.channel.json
📚 Documentation
The main UI component is in src/app/page.tsx. You can:
- Modify the theme colors and styling
- Add new frontend actions
- Customize the CopilotKit sidebar appearance
Otherwise, check out the documentation relevant to your task:
- Agno Documentation - Learn more about Agno and its features
- CopilotKit Documentation - Explore CopilotKit's capabilities
- Next.js Documentation - Learn about Next.js features and API
- YFinance Documentation - Financial data tools
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 Agno agent is running on port 8000
- Your OpenAI API key is set correctly
- Both servers started successfully
Python Dependencies
If you encounter Python import errors:
cd agent
uv sync
CopilotKit Intelligence & Threads (Optional)
CopilotKit Intelligence adds durable thread history and cross-session memory to
your agent. It requires a COPILOTKIT_LICENSE_TOKEN, a
CPK_INTELLIGENCE_API_KEY, and a running local
Intelligence stack (Docker Desktop + a local Intelligence repo checkout).
Prerequisites
- Docker Desktop running
- A
COPILOTKIT_LICENSE_TOKEN(obtain from CopilotKit Cloud) - A
CPK_INTELLIGENCE_API_KEYfor the Intelligence project - The Intelligence repo cloned
locally. The
docker-compose.intelligence.ymldefaults to a sibling directory at../../../Intelligencerelative to this starter; override with theINTELLIGENCE_REPOenv var if your checkout is elsewhere.
Start the intelligence stack
# From inside this starter directory:
docker compose -f docker-compose.intelligence.yml up -d --wait
First run builds the intelligence image from source (may take several minutes).
Verify the stack is healthy
docker compose -f docker-compose.intelligence.yml ps
All three services (postgres, redis, intelligence) should show healthy.
Set environment variables
Add the following to your .env file:
COPILOTKIT_LICENSE_TOKEN=your-license-token-here
CPK_INTELLIGENCE_API_KEY=your-project-api-key-here
INTELLIGENCE_API_URL=http://localhost:4202
INTELLIGENCE_GATEWAY_WS_URL=ws://localhost:4402
Then start the dev server as usual (npm run dev). Thread history and memory
features are activated automatically when CPK_INTELLIGENCE_API_KEY is set.
Stop / reset
# Stop without removing data:
docker compose -f docker-compose.intelligence.yml down
# Full reset (removes postgres + redis volumes):
docker compose -f docker-compose.intelligence.yml down -v