Describe the bug
Upgraded a Node.js voice agent from @livekit/agents@1.5.5 to 1.6.0 specifically to try the new simulation feature, since the 1.6.0 changelog describes shipping SimulationContext, onSimulationEnd, and --simulation/LIVEKIT_AGENT_NAME_OVERRIDE handling for Node.
Running lk agent simulate <entrypoint.ts> --scenarios scenarios.yaml --yes against a real LiveKit Cloud project:
The Node worker starts and connects to LiveKit Cloud successfully.
It registers under the simulation agent name (log shows "agentNameIsEnv":true, confirming LIVEKIT_AGENT_NAME_OVERRIDE is being honored correctly).
A simulation run is created and the scenario is dispatched to the worker.
The job then fails immediately — before any conversation turns happen — with a compatibility-check error (see log below).
Relevant log output
{"level":30,"msg":"starting worker","version":"1.6.0"}
{"level":20,"msg":"connected to LiveKit server"}
{"level":30,"id":"AW_Jt4aoy9nxcmp","agentName":"simulation-co6h7v7b","agentNameIsEnv":true,"msg":"registered worker"}
✓ Agent registered (5.999s)
✓ Simulation created (1.09s)
✓ Loaded 1 scenarios from scenarios.yaml ("CareDesk fail-fast checkpoint")
Error: cannot verify the agent's SDK supports scenario dispatch (needs livekit-agents >= 1.6.6):
get_framework_info did not return a python SDK version. Upgrade the agent's livekit-agents.
Describe your environment
System:
OS: Windows 11 10.0.26200
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
Binaries:
Node: 24.8.0
npm: 11.6.0
npmPackages:
@livekit/agents: ^1.6.0 => 1.6.0
@livekit/agents-plugin-deepgram: ^1.6.0 => 1.6.0
@livekit/agents-plugin-elevenlabs: ^1.6.0 => 1.6.0
@livekit/agents-plugin-openai: ^1.6.0 => 1.6.0
@livekit/noise-cancellation-node: ^0.1.10 => 0.1.10
@livekit/protocol: ^1.49.0 => 1.50.4
@livekit/rtc-node: ^0.13.30 => 0.13.32
Minimal reproducible example
No response
Additional information
No response
Describe the bug
Upgraded a Node.js voice agent from @livekit/agents@1.5.5 to 1.6.0 specifically to try the new simulation feature, since the 1.6.0 changelog describes shipping SimulationContext, onSimulationEnd, and --simulation/LIVEKIT_AGENT_NAME_OVERRIDE handling for Node.
Running lk agent simulate <entrypoint.ts> --scenarios scenarios.yaml --yes against a real LiveKit Cloud project:
The Node worker starts and connects to LiveKit Cloud successfully.
It registers under the simulation agent name (log shows "agentNameIsEnv":true, confirming LIVEKIT_AGENT_NAME_OVERRIDE is being honored correctly).
A simulation run is created and the scenario is dispatched to the worker.
The job then fails immediately — before any conversation turns happen — with a compatibility-check error (see log below).
Relevant log output
{"level":30,"msg":"starting worker","version":"1.6.0"}
{"level":20,"msg":"connected to LiveKit server"}
{"level":30,"id":"AW_Jt4aoy9nxcmp","agentName":"simulation-co6h7v7b","agentNameIsEnv":true,"msg":"registered worker"}
✓ Agent registered (5.999s)
✓ Simulation created (1.09s)
✓ Loaded 1 scenarios from scenarios.yaml ("CareDesk fail-fast checkpoint")
Error: cannot verify the agent's SDK supports scenario dispatch (needs livekit-agents >= 1.6.6):
get_framework_info did not return a python SDK version. Upgrade the agent's livekit-agents.
Describe your environment
System:
OS: Windows 11 10.0.26200
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
Binaries:
Node: 24.8.0
npm: 11.6.0
npmPackages:
@livekit/agents: ^1.6.0 => 1.6.0
@livekit/agents-plugin-deepgram: ^1.6.0 => 1.6.0
@livekit/agents-plugin-elevenlabs: ^1.6.0 => 1.6.0
@livekit/agents-plugin-openai: ^1.6.0 => 1.6.0
@livekit/noise-cancellation-node: ^0.1.10 => 0.1.10
@livekit/protocol: ^1.49.0 => 1.50.4
@livekit/rtc-node: ^0.13.30 => 0.13.32
Minimal reproducible example
No response
Additional information
No response