Important If you use a

LIVEKIT_URL

,

LIVEKIT_API_KEY

, and

LIVEKIT_API_SECRET

from the same project that you use for local development, your local worker will join the same pool as your production workers. This means real users could be connected to your local worker. This is usually not what you want so make sure to use a different project for local development. This is from the livekit documentation, if i use same

LIVEKIT_URL

but different api and api secret then will the agents be seperated?

It seems likely that using different API keys and secrets alone will not separate your local and production agents. According to LiveKit documentation, you need to use a different project for local development to ensure that your local and production agents do not join the same pool. Different keys won’t guarantee separation, as mentioned in the Slack discussion. Would you like more detail on how to set up separate projects for local and production environments? Sources: - Slack Discussion - LiveKit documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.