Skip to main content

livekit-plugins-alkove

Alkove for LiveKit Agents: Focus keeps the user's voice and removes the others and the noise, Cue finds where they speak. Both run on the agent's CPU, with no server and no key, with the chain and the speech rules of Alkove's web SDK.

Install

pip install livekit-plugins-alkove
python my_agent.py download-files     # Focus and Cue into the cache, checked by their sha256

Use

from livekit.agents import AgentSession, room_io
from livekit.plugins import alkove

session = AgentSession(vad=alkove.VAD.load(), ...)
await session.start(
    agent,
    room=ctx.room,
    room_options=room_io.RoomOptions(
        audio_input=room_io.AudioInputOptions(noise_cancellation=alkove.Focus()),
    ),
)
  • alkove.Focus() is a rtc.FrameProcessor. It keeps the closest voice, or with voiceprint= the voice of that print; strength= and normalize= work as in the web SDK. It works at the session's sample rate (24 kHz by default) and gives each frame back at the size it came in, about 37 ms behind: whole 10 ms frames, as LiveKit's gain control needs. The models are read from the cache download-files filled when it is created. In console mode LiveKit reads the microphone itself, without RoomIO: Focus is not applied there, Cue is. Test Focus in a room (dev).
  • alkove.VAD.load() gives one speech probability every 30 ms, with speech=alkove.SpeechParams(confidence=0.5, exit_confidence=0.1, start_secs=0.2, stop_secs=0.6) by default. It counts as the turn detector's min_silence_duration (stop_secs). Behind Focus, it hears only the user.

To keep one person's voice rather than the closest one, make their print with Timbre, from 1.5 s of their voice or more at 16 kHz:

from alkove import Models, Timbre

models = Models.load(["focus", "cue", "timbre"])
me = Timbre(models).embed(pcm)
focus = alkove.Focus(models=models, voiceprint=me)

The models are loaded once per process and shared by every session. Pass models=alkove.Models.load(["focus", "cue"], dir=...) to read them from your own folder.

Tested with livekit-agents 1.8.8.

License

Apache-2.0. See NOTICE.

Metadata

Release files for livekit-plugins-alkove 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for livekit-plugins-alkove 0.3.0
File Size Uploaded Provenance
livekit_plugins_alkove-0.3.0.tar.gz 9.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for livekit-plugins-alkove 0.3.0
File Interpreter ABI Platform
livekit_plugins_alkove-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 22.7 kB

Release files / livekit_plugins_alkove-0.3.0.tar.gz

Download URL livekit_plugins_alkove-0.3.0.tar.gz
Size 9.9 kB
Tags Source
SHA-256 checksum
How to use checksums
b168db312b1566b8db87259dd62fd088f3b21e97daed1fbd3b758e47d587c1b8
BLAKE2b-256 checksum
How to use checksums
2d4c8d5fe1bf505b0656c2070f8410964cd64884126bf3ea9951284f8e3518b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Release files / livekit_plugins_alkove-0.3.0-py3-none-any.whl

Download URL livekit_plugins_alkove-0.3.0-py3-none-any.whl
Size 12.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a08b3d276e34fef6c7778b80aacce67b43085756f69099ed0c39b8ea70b60bc6
BLAKE2b-256 checksum
How to use checksums
7ebe0f2f9b2b8c227e0625efa578f2720eb96d651e13437a662e4e46abd6527a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Security for livekit-plugins-alkove 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for livekit_plugins_alkove-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page