Authorization notice. Openspline is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. LiveKit API secret and OpenAI key must stay on the server side of the agent.
Who it is forA team running a LiveKit voice agent that needs a face shown inside its existing room frontend.
The problemLiveKit rooms carry audio only, so the agent has no visible presence for participants.
The outcomeThe avatar appears in the same LiveKit room as the agent, driven by its audio.
What you need first
- A portrait image of the face to animate, with rights to use it
- Python 3.x or Node 20+ for the SDK
- Either an OpenSpline Cloud API key or a Linux or WSL2 machine with an NVIDIA GPU
- An existing voice AI agent or a TTS provider that outputs PCM audio
Steps
- Run
pip install 'livekit-agents[openai]==1.8.3'. - Set
OPENAI_API_KEY,LIVEKIT_URL,LIVEKIT_API_KEY, andLIVEKIT_API_SECRET. - Create
avatar = AvatarSession("portrait.jpg", client=Openspline(quality="low"))and callawait avatar.start(agent_session, room=ctx.room)before your existing session starts. - Run
PORTRAIT=portrait.jpg python examples/python/livekit_agent.py dev. - Join the room from your normal LiveKit frontend and confirm the avatar speaks.
Prompt for your agent
Use the openspline repo (github.com/openspline/openspline) to attach an AvatarSession to the LiveKit agent in <path-to-agent>, using portrait <path-to-portrait.jpg>. Start the avatar before agent_session.start and confirm the avatar is visible in the room.
Caveat. The README says the native service includes LiveKit support, so check that your setup uses that service before relying on this connector.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page