Hi LiveKit team 👋
I'm from Avaluma, a real-time avatar provider. We've built a LiveKit Agents integration for our avatars and would like to contribute it upstream so Avaluma can sit alongside the other avatar providers in the docs.
What it is
A remote avatar plugin (livekit-plugins-avaluma) that follows the conventions of the existing avatar plugins (bey/tavus/anam/…):
- PEP 420 namespace package:
from livekit.plugins.avaluma import AvatarSession
- Standard
AvatarSession.start(agent_session, room, ...) API
- Audio via
DataStreamAudioOutput with publish_on_behalf and wait_remote_track=KIND_VIDEO
- Agent/user turn-taking state forwarded to the avatar over RPC
- Ships
py.typed, Apache-2.0 licensed
PR
I've opened a PR with the plugin, an example agent, and the extras / workspace / lock wiring. It passes ruff check, ruff format --check, and mypy --strict.
Happy to
- sign the CLA,
- align the version with the monorepo's release scheme,
- coordinate the PyPI publish under the LiveKit org,
- provide test credentials / a demo so you can validate the integration,
- and add the docs page for the avatar integrations list.
Thanks!
Hi LiveKit team 👋
I'm from Avaluma, a real-time avatar provider. We've built a LiveKit Agents integration for our avatars and would like to contribute it upstream so Avaluma can sit alongside the other avatar providers in the docs.
What it is
A remote avatar plugin (
livekit-plugins-avaluma) that follows the conventions of the existing avatar plugins (bey/tavus/anam/…):from livekit.plugins.avaluma import AvatarSessionAvatarSession.start(agent_session, room, ...)APIDataStreamAudioOutputwithpublish_on_behalfandwait_remote_track=KIND_VIDEOpy.typed, Apache-2.0 licensedPR
I've opened a PR with the plugin, an example agent, and the extras / workspace / lock wiring. It passes
ruff check,ruff format --check, andmypy --strict.Happy to
Thanks!