Is anyone else having issues with Livekit Console mode? Agents Starting console mode 🚀 194339.663 DEBUG asyncio Using selector: KqueueSelector 194339.665 DEBUG livekit.agents cleaning prometheus multiprocess directory {"path": "/var/folders/7k/gf450lg125vc_nj332v_j6fr0000gn/T/prometheus_multiproc"} INFO livekit.agents starting worker {"version": "1.5.2", "rtc-version": "1.1.5"} 194339.666 INFO livekit.agents plugin registered {"plugin": "livekit.plugins.cartesia", "version": "1.5.2"} INFO livekit.agents plugin registered {"plugin": "livekit.plugins.deepgram", "version": "1.5.2"} 194339.667 INFO livekit.agents plugin registered {"plugin": "livekit.plugins.elevenlabs", "version": "1.5.2"} INFO livekit.agents plugin registered {"plugin": "livekit.plugins.openai", "version": "1.5.2"} 194339.668 INFO livekit.agents plugin registered {"plugin": "livekit.plugins.silero", "version": "1.5.2"} INFO livekit.agents plugin registered {"plugin": "livekit.plugins.turn_detector.base", "version": "1.5.2"} 194339.669 INFO livekit.agents starting inference executor 194339.686 INFO livekit.agents initializing process {"pid": 18037, "inference": true} SENTRY_DSN not set, error tracking disabled 194345.074 INFO livekit.agents process initialized {"pid": 18037, "inference": true, "elapsed_time": 5.39} 194345.079 INFO livekit.agents HTTP server listening on :62108 194345.084 WARNING livekit.agents no warmed process available for job, waiting for one to be created {"job_id": "mock-job-f29673714788"} 194345.095 INFO livekit.agents initializing job runner {"tid": 1795683} 194345.145 DEBUG asyncio Using selector: KqueueSelector 194345.146 INFO livekit.agents job runner initialized {"tid": 1795683, "elapsed_time": 0.05} Have checked on multple computers and all doing the same, stuck as if its waiting for a job?

Hi Charlton Santana, ⚠️ This channel will be deleted soon ⚠️ Please use our new community at https://community.livekit.io for technical discussions and to post technical questions. The Slack community is not going away, but we are migrating technical questions to our new forum. Please see full details here.

Just a note on this. Pinning back to 1.5.1 from 1.5.2 fixed this. Haven't seen anything in the changelog regarding this in the newer version. But will test with .3 and .4 today.