Version Packages by github-actions[bot] · Pull Request #1690 · livekit/agents-js

github-actions · 2026-06-02T19:19:27Z

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@livekit/agents@1.4.6

Patch Changes

Add the agent participant SID as an X-LiveKit-Agent-Id header on inference requests, alongside the existing room and job ID headers, when running inside a job context. - #1687 (@adrian-cowham)
Defer AMD listening until the participant audio track is subscribed, and for SIP participants until sip.callStatus is active, so ringback and early media no longer consume the no-speech budget. After AMD settles on a machine verdict with interruptOnMachine, skip the normal auto-reply triggered by user-turn completion so it no longer races with — and interrupts — the caller's own generateReply (e.g. leaving a voicemail). - #1639 (@rosetta-livekit-bot)

Complete the AMD verdict-emission port: add waitUntilFinished and maxEndpointingDelayMs options and gate emission on both post-speech silence and end-of-turn (machine/uncertain verdicts wait for the turn detector or a fallback backstop; a confident human releases on silence alone). Settle no_speech_timeout as uncertain instead of machine-unavailable. Treat the classifier LLM's tool calls as authoritative — no longer resurrect a verdict by parsing free-text content emitted alongside an uncertain/postpone tool call.

Wire AMD into the recognition-hook layer the way the Python framework does: AgentActivity now drives AMD via onUserSpeechStarted(), onUserSpeechEnded(silenceDurationMs), and onTranscript(text, source) from its VAD/STT hooks, instead of AMD snooping the derived UserStateChanged/UserInputTranscribed session events. This gives AMD the VAD's real silenceDuration directly, so post-speech timers and reported delays are anchored on the true speech-end time rather than skewed by VAD/event latency.

Port the AMD classification prompt verbatim from the Python framework — restoring the task description, category definitions (machine-vm = leaving a message IS possible; machine-unavailable = NOT possible), and the few-shot examples that steer borderline cases (hours-of-operation → uncertain, "press 1" → machine-ivr, call-screening → machine-ivr) — and pass the raw transcript as the user message so it matches the prompt's Input:/Output: pattern.
Support granular recording options in AgentSession.start. The record option now accepts boolean | RecordingOptions ({ audio, traces, logs, transcript }); a boolean maps to all-on/all-off and a partial object merges onto all-on, so omitted keys default to true. Each category independently gates audio capture, trace export, log export, and transcript upload, mirroring the Python SDK and matching the documented granular form. - #1702 (@anzemur)
Guard inference agent ID header lookup until the room is connected. - #1700 (@rosetta-livekit-bot)
Close active RecorderIO during job session-end cleanup before generating the session report. - #1682 (@rosetta-livekit-bot)
Align AgentSession.start recording with the Python SDK's primary-session behavior. The primary/secondary designation now happens in start() before initRecording, so a demoted secondary session never configures cloud recording. A non-primary session whose record argument was not explicitly given now silently disables its recording (instead of throwing); it still throws only when record was passed explicitly, matching Python's record_is_given semantics. - #1704 (@toubatbrian)
Add TcpSessionTransport, a SessionTransport that frames protobuf session messages over a raw TCP socket (4-byte big-endian length prefix, 1 MiB cap, TCP_NODELAY), mirroring the Python implementation. Also handle the updateIo session request in SessionHost, toggling input/output audio and transcription. This is the transport plumbing that lets a local broker (e.g. the LiveKit CLI session daemon) drive a Node agent over TCP. - #1693 (@toubatbrian)