crooked-dawn-90821
09/24/2025, 11:26 AMtall-airline-16756
09/24/2025, 11:26 AMtall-airline-16756
09/24/2025, 11:27 AMws_url, api_key, and api_secret all correctly set?
• Are you using explicit dispatch mode by setting the agent_name field in WorkerOptions?
• Is the worker showing signs of high system load or maybe in drain mode?
• Have you set up a request_fnc that could be rejecting job requests?
Once you’ve had a chance to check these, just let me know. I’m here to help you get this sorted out!
Sources: livekit-agents/livekit/agents/worker.py | Dispatching agents | LiveKit Docs | agents/src/cli.ts | Worker options | LiveKit Docs | Worker lifecycle | LiveKit Docscrooked-dawn-90821
09/24/2025, 11:30 AMtall-airline-16756
09/24/2025, 11:31 AMagent_name field (in Python) or agentName (in Node.js) within the WorkerOptions when initializing your agent. Here are some examples to guide you:
Python:
from livekit.agents import WorkerOptions, cli
if __name__ == "__main__":
cli.run_app(
WorkerOptions(
entrypoint_fnc=entrypoint,
agent_name="inbound-agent", # Define agent name here
)
)
Node.js:
const opts = new WorkerOptions({
entrypoint: entrypoint,
agentName: "outbound-caller", // Define agent name here
});
Once you’ve set the agent name, you can dispatch the agent to a room either explicitly using the AgentDispatchService API or by including the agent configuration in the room’s access token. If you have any questions or need a hand with this, just let me know—I’m here to help!
Sources: examples/agent_dispatch.py | examples/agent-dispatch/index.ts | Dispatching agents | LiveKit Docs | Agent dispatch | LiveKit Docs | Accepting incoming calls | LiveKit Docs