To create a test environment for your existing deployed project, you have several options depending on your requirements: • Sandbox Environment: LiveKit provides a sandbox environment for testing and prototyping. This is useful if you want to explore features or test without affecting your production setup. • Separate Projects: You can create a new project and manage it using the LiveKit CLI. This allows you to maintain separate environments for production and testing. Use the following commands to add and switch between projects:

lk project add --api-key <key> --api-secret <secret> <project_name>
lk project set-default <project_name>

• Same Project, Different Configurations: You can use the same project credentials with different configurations for testing. Set up environment variables to point to your LiveKit server and use them in your test applications:

export LIVEKIT_API_SECRET=SECRET
export LIVEKIT_API_KEY=KEY
export LIVEKIT_URL=YOUR_LIVEKIT_URL

• Testing Tools: The LiveKit CLI provides utilities for testing, such as creating rooms and simulating participants. These tools can help you test within your existing project infrastructure. If you need strict isolation between production and testing, creating a new project with separate authentication credentials is recommended. Otherwise, you can use the same project with different configurations for simpler setups. Sources: Authentication Examples | livekit/livekit_composite | DeepWiki | CLI Setup | LiveKit Docs | autocomplete/fish_autocomplete | Custom recording templates | LiveKit Docs | agent/.env.sample