Thanks — I see the UI message: “Session ended. Agent did not join the room.” I’ll help troubleshoot that. Quick checks to start with (please try these and share results/logs if the issue persists): 1. Is the agent process running? ◦ If you’re running locally, start the agent in dev mode:

uv run agent.py dev

and confirm the console shows registered worker. ◦ Don’t use

uv run agent.py console

for live sessions — console mode does not connect to LiveKit. 1. Check agent logs for errors or crashes at startup or when a job is dispatched. Copy any error lines you see. 2. Ensure the agent can reach the LiveKit server and has correct credentials (API key/secret or configured environment variables). For self-hosted setups, verify network connectivity to the LiveKit endpoint. 3. If multiple developers or agents exist on the same project, ensure

agent_name

is unique so jobs dispatch to the correct worker. 4. Verify the agent hasn’t been immediately shut down after starting (unhandled exceptions or graceful-shutdown issues). If you see crash traces, paste them here. If you can, please provide: • How you start the agent (exact command). • Recent agent logs (startup and any errors). • Whether this is LiveKit Cloud or a self-hosted deployment. • Any recent changes (config, network, or code). With those details I’ll give targeted next steps. Sources: Introduction | LiveKit Documentation | Server lifecycle | LiveKit Documentation | Build Your First AI Voice Agent in Python: Complete Tutorial | LiveKit | Build Your First AI Voice Agent in Python: Complete Tutorial | LiveKit | Avoiding crosstalk when multiple developers share a LiveKit project | LiveK..., with interactive elements