Skip to content
← Tools / Skills
ToolDaily/10 trustVerified
Pipecat logo

Pipecat

Open-source framework for building real-time voice and multimodal AI agents.

Visit official site →

About

Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents, maintained by Daily. You compose STT, LLM, and TTS services into a frame-based pipeline — audio flows in, text reasoning happens in the middle, speech flows back out — with the framework handling voice activity detection, turn-taking, interruptions (barge-in), and function calling. It supports 50+ AI service integrations, multiple transports (WebRTC via Daily or LiveKit, WebSocket, WhatsApp, Twilio), and multi-agent patterns (handoff, parallel fan-out, sidecar workers) that can run locally or distributed across machines.

What it can do

  • **Frame-based composable pipelines** (README-verified): voice-first orchestration of STT, LLM, TTS, transport, and processors, with interruption handling, VAD, and turn-taking built in.
  • **50+ pluggable service integrations**: STT (Deepgram, AssemblyAI, OpenAI Whisper, Groq, ...), LLMs (Anthropic, OpenAI, Gemini, Groq, Ollama, ...), TTS (Cartesia, ElevenLabs, OpenAI, Kokoro, ...), plus speech-to-speech services (OpenAI Realtime, Gemini Multimodal Live, AWS Nova Sonic), telephony serializers (Twilio, Telnyx, Vonage), and video avatars (Tavus, HeyGen, Simli).
  • **Multi-agent ready**: each pipeline is an agent — compose with handoff, parallel fan-out, sidecar workers, or distributed deployments. **Pipecat Flows** (built in) for structured conversations, **Whisker** real-time pipeline debugger, **Tail** terminal dashboard, official client SDKs (JS/React/React Native/Swift/Kotlin/C++/ESP32), Claude Code skills, and **Pipecat Cloud** for deployment.

Setup

Quickest path — the CLI scaffolds a runnable bot in under a minute (README-verified):

```bash

uv tool install "pipecat-ai[cli]"

pipecat init quickstart

```

Or add to an existing project:

```bash

pip install pipecat-ai

```

A minimal voice assistant pipeline looks like this:

```python

from pipecat.pipeline.pipeline import Pipeline

from pipecat.pipeline.runner import PipelineRunner

from pipecat.pipeline.task import PipelineTask

pipeline = Pipeline([

transport.input(), # listen to the user

stt, # speech -> text (e.g. Deepgram)

llm, # reason + respond (e.g. OpenAI)

tts, # text -> speech (e.g. Cartesia)

transport.output(), # send audio back

])

await PipelineRunner().run(PipelineTask(pipeline))

```

Full quickstart: https://docs.pipecat.ai/getting-started/quickstart

Prerequisites

Python 3.10+ recommended. API keys for the STT, LLM, TTS, and transport services you wire in (e.g. Deepgram, OpenAI/Anthropic, Cartesia/ElevenLabs, Daily) — the framework is free but the services it orchestrates are mostly paid. For self-hosted WebRTC in production you will also need TURN server infrastructure.

Use cases

voice-assistantsvoice-agentscustomer-support-botsai-companionsmeeting-assistantsmultimodal-chatbotsinteractive-storytellingtelephony-bots

Works with

Claude CodeCodexCursorWindsurfAider

Trust score — 9/10

/10 trustVerified

16,401 stars, BSD-2-Clause confirmed in the repo's LICENSE (Copyright 2024–2026 Daily), very actively maintained (pushed 2026-10-12), with thorough docs (docs.pipecat.ai) and a verified quickstart path (`pipecat init quickstart`). Capability claims cross-checked against the README's own service tables and independent writeups. Docked two points because a working deployment requires paid third-party API keys for the STT/LLM/TTS services it orchestrates, and self-hosted production WebRTC still needs TURN infrastructure — real costs the marketing glosses over.

★ 16,401 GitHub stars

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
7.9/10
Maintenance · recency, releases, issue load
9.0/10
Openness · license + docs
10.0/10
Manual review · sanity read + red-flag check
8.0/10
  • · 16,401 GitHub stars (log-scaled vs catalog peers)
  • · last push 0d ago; 33 releases/12mo; 394 open issues
  • · manual review: deployments require paid third-party API keys; self-hosted WebRTC needs TURN infra

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.