Is there a tracker of sorts for feature parity bet...
# ask-aim
millions-journalist-75191
02/27/2026, 1:24 PMIs there a tracker of sorts for feature parity between the python and nodejs server sdks?
t
tall-airline-16756
02/27/2026, 1:24 PMThanks for reaching out, Aaron. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
02/27/2026, 1:25 PMThanks — you're asking whether there's a feature-parity tracker comparing the Python and Node.js server SDKs. I don't have a public tracker on hand.
To help quickly, could you tell me which of these you mean or care most about?
• Overall API parity (same methods/classes and behavior)
• Specific features (e.g., room management, participant controls, recording, webhooks, authentication helpers)
• Stability / release parity (which versions have matching features)
• Examples and sample code parity
• Something else (please describe)
If you tell me which areas matter, I can either:
• Look for or create a concise comparison for those features, or
• Suggest a simple checklist you can use to verify parity across the two SDKs.
Which would you prefer, and which features should I focus on?
m
millions-journalist-75191
02/27/2026, 1:26 PMIs there a channel to track this maybe? An issues list for contributors? for example the turn detection feature
t
tall-airline-16756
02/27/2026, 1:26 PMThanks — you're asking whether there's a public place to track feature parity (for example, turn-detection) between the Python and Node.js server SDKs and whether contributors are tracking it.
I don't have a single, dedicated "feature-parity tracker" to point to. However, here are practical places you can use to track or raise parity items and follow contributor discussion:
• Check the GitHub repos for issues and feature requests:
◦ livekit/agents (Python): https://github.com/livekit/agents
◦ livekit/agents-js (Node.js): https://github.com/livekit/agents-js
Look for existing issues, or open a new issue titled something like “Feature parity: turn-detection” so contributors can discuss and triage it.
• Join the LiveKit community Slack to discuss features directly with maintainers and other contributors: https://livekit.io/join-slack
Slack is a good place to surface parity concerns and get guidance on status, priorities, or workarounds.
If you’d like, I can help with either of these next steps:
• Search the two repos for existing issues related to turn detection and report back what I find.
• Draft an issue template you can paste into GitHub that outlines the parity gap (what exists in Python, what's missing in Node.js, and suggested behavior).
Which would you prefer?
Sources: Agents (Python) | livekit/livekit_composite | DeepWiki | Improving voice AI's turn detection with transformers
2 Views