All videos
0:00 / 0:00
research

Turn Any LangGraph Agent Into a Voice Agent in Minutes

LangChain23 June 2026Watch on YouTube

Part of series

Ep. 6 · LangSmith Engine

LangChain's LangSmith Engine automatiseert het verbeteren van AI-agents door productie-traces om te zetten in geheugen en fixes.

View the series

Description

Caroline di Vittorio, software engineer at LangChain, walks through how to take an existing LangGraph multi-agent system and wire it into a fully functional voice agent using Pipecat — without rebuilding your graph from scratch. She covers the key architectural change required (dropping the checkpointer and making the graph stateless), how Pipecat handles speech-to-text, text-to-speech, voice activity detection, and interruptions out of the box, and how to get complete LangSmith traces that include audio recording, latency, and costs across every layer of the pipeline. Turn Any LangGraph Agent Into a Voice Agent in Minutes 0:00 Why voice agents are just a new modality for your existing agent 0:40 What Pipecat does and how it fits into the stack 1:10 The demo agent: LangGym customer support with four specialized sub-agents 1:47 How the multi-agent graph routes and maintains state 2:35 Testing the text agent with FastAPI 3:04 Watching the triage and cancellation agents hand off in real time 3:24 Inspecting the LangSmith trace for the text agent run 4:09 Time to add voice: swapping in Pipecat 4:20 Walking through the basic Pipecat pipeline (STT, LLM, TTS) 5:07 Voice activity detection and interruption handling explained 6:01 Replacing the OpenAI LLM layer with the LangGraph agent 7:20 The checkpointer problem: why stateful LangGraph breaks with Pipecat 8:01 Making the graph stateless: deriving active agent from messages 10:13 How the adapter passes context between Pipecat and LangGraph 10:38 Running the full voice agent demo 11:40 What's missing from the first trace: STT, TTS, audio, latency 12:22 Adding the LangSmith span processor for complete Pipecat tracing 14:42 Adding audio recording and seeing it in the trace UI 16:05 Prompting differences between text and voice agents Referenced docs: → Trace Pipecat application: https://docs.langchain.com/langsmith/trace-with-pipecat → Quickstart - Pipecat: https://docs.pipecat.ai/pipecat/get-started/quickstart → Quickstart - LangChain: https://docs.langchain.com/oss/python/langgraph/quickstart → Demo repo: https://github.com/langchain-ai/pipecat-langgraph-example Resources: → LangGraph: https://www.langchain.com/langgraph → LangSmith: https://www.langchain.com/langsmith → Pipecat docs: https://docs.pipecat.ai

What you'll learn

  • Voice agents are simply a new modality for existing LangGraph agents without rebuilding the underlying logic
  • Pipecat adds speech handling (STT, TTS, voice activity detection, interruptions) and integrates directly with LangGraph agents
  • LangGraph agents must be made stateless for Pipecat by removing the checkpointer and deriving the active agent from messages
  • Complete tracing is possible with LangSmith, including audio, latency and costs across each pipeline layer

Frequently asked questions

What is the main architectural change needed to make a LangGraph agent suitable for Pipecat?
The checkpointer must be removed and the graph made stateless by deriving the active agent from messages instead of maintaining internal state.
Which voice processing features does Pipecat provide out of the box?
Pipecat provides speech-to-text, text-to-speech, voice activity detection and interruption handling without requiring separate implementation.
How can you see complete traces with audio and latency in LangSmith for a Pipecat voice agent?
Add a LangSmith span processor to the Pipecat pipeline to enable full tracing, including audio recordings and performance metrics across each layer.
What is the advantage of Pipecat for converting existing text-based agents to voice agents?
Pipecat eliminates rework because you can keep the underlying LangGraph agent unchanged and simply add the voice interface layer.

Topics

Related reads