Hi

Thanks for reaching out, YASH. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Agent it not starting up in console using

python agent.py console

it stucks at

participant = await ctx.wait_for_participant()

Thanks — I’m responding to the issue where

python agent.py console

hangs at

participant = await ctx.wait_for_participant()

. What’s happening • Console mode runs entirely locally and does not connect to LiveKit Cloud, so there will be no remote participant to join a room. •

ctx.wait_for_participant()

waits indefinitely for a participant, which will never occur in console mode. How to proceed • If you want to interact in the terminal (text or mic) remove or skip

ctx.wait_for_participant()

and run the agent in console mode with:

uv run agent.py console

The agent will accept input directly in the terminal without waiting for a LiveKit participant. • If you need full RTC behavior (wait for participants, SIP, or room connections), run the agent in dev mode and test via the Agent Console / LiveKit Cloud instead of console mode. If you’d like, tell me whether you want: • Terminal testing (I’ll show the minimal code change to skip

wait_for_participant()

), or • Full RTC testing (I’ll guide you to start the agent in dev mode and how to join a room). Sources: Avoiding crosstalk when multiple developers share a LiveKit project | LiveK... | Job lifecycle | LiveKit Documentation | Server startup modes | LiveKit Documentation | Google AI and LiveKit | LiveKit Documentation | Build Your First AI Voice Agent in Python: Complete Tutorial | LiveKit, with interactive elements