magnificent-furniture-73003
09/18/2025, 4:00 PMtall-airline-16756
09/18/2025, 4:00 PMtall-airline-16756
09/18/2025, 4:01 PMdev mode within the same LiveKit project. This setup is totally supported for development, and the two agents can happily coexist.
That said, the free tier gives you a quota of 1,000 agent session minutes. It’s a bit unclear whether running both agents at the same time will count against this limit or if dev mode usage is tracked differently. To stay on the safe side, I recommend keeping an eye on your usage dashboard to see if dev mode sessions are using up your agent minutes.
If you want me to explain more about how session minutes are calculated for local development agents, just let me know—I’m here to help!
Sources: Voice AI quickstart | LiveKit Docs | LiveKit Pricingmagnificent-furniture-73003
09/18/2025, 4:03 PMtall-airline-16756
09/18/2025, 4:03 PMdev mode and the deployed agent are connecting to the same LiveKit server instance. Since, by default, they aren’t separated by environment, both agents end up registering and responding to the same room events, which causes them to overlap in behavior.
To help you avoid this, here are a few friendly suggestions:
• You might try running your local dev agent against a separate LiveKit server instance—for example, a local server using livekit-server --dev.
• Another approach is to use room metadata filters in your agent logic, so only one agent responds to specific events.
• Also, it’s a good idea to make sure the local dev agent isn’t left running when you’re testing or deploying to production.
Please feel free to reach out if you’d like me to walk you through any of these steps or if you have any other questions. I’m here to help!
Sources: Running LiveKit locally | LiveKit Docs | README.md | Voice AI quickstart | LiveKit Docs | Voice AI quickstart | LiveKit Docs | README.md