This repository provides runnable Python examples for building voice, video, and telephony agents using LiveKit Agents. It targets developers creating production-ready AI agents, offering practical demonstrations of real-world patterns and best practices to accelerate development.

How It Works

The project showcases the LiveKit Agents framework through diverse examples, from single-agent interactions to multi-agent orchestration and multimodal capabilities. It highlights core concepts like pipeline customization (STT, LLM, TTS), tool invocation, and context management. Examples are organized with YAML frontmatter for easy discovery, including focused demos and full-stack applications with frontends.

Quick Start & Requirements

• Install: Clone repo, create/activate Python venv, pip install -r requirements.txt.
• Prerequisites: Python 3.10+, pip/uv, LiveKit Account. Node.js 18+ and pnpm for frontend demos.
• Setup: .env file with LiveKit credentials (LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET) and optional provider API keys.
• Run: python docs/examples/listen_and_respond/listen_and_respond.py console for interactive voice.
• Links: LiveKit Agents Docs: docs.livekit.io/agents, GitHub: github.com/livekit/agents, Cloud: cloud.livekit.io.

Highlighted Details

• Features 50+ focused demos and 20+ production applications with frontends.
• Extensive examples cover Fundamentals, Multi-Agent Systems, Telephony, Pipeline Customization, Vision/Multimodal, Avatars, Translation, Metrics, Events, State Management, and Advanced Integrations.
• Demonstrates broad provider support across LLM, STT, TTS, VAD, Avatar, Vision, and Realtime services.
• Includes full-stack applications like "Dungeons & Agents" (voice-driven RPG) and "Doheny Surf Desk" (phone booking system).

Maintenance & Community

Developed by the LiveKit team, contributions via issues/PRs are welcomed. Specific community channels or detailed contributor information are not provided.

Licensing & Compatibility

The repository's license is not explicitly stated in the README, requiring clarification for adoption, especially concerning commercial use or closed-source integration.

Limitations & Caveats

The README does not detail specific limitations. However, reliance on third-party API keys implies potential costs and setup complexity. Frontend development requires Node.js/pnpm. The absence of a stated license is a significant adoption blocker.