Skip to main content
Once your Avatar Server and LiveKit Agent are running, use one of two test clients to verify the full pipeline end-to-end. Both clients open a LiveKit room, connect to your agent, and display the avatar video stream so you can confirm that audio, video, and agent logic are all working correctly.

Avaluma Test Client

Works with any LiveKit setup — Cloud or self-hosted. Enter your LiveKit credentials directly in the client and connect instantly.

LiveKit Agent Playground

For LiveKit Cloud projects. Select your project and enter your agent name to connect without manually entering credentials.

​
Connect with the Avaluma Test Client

The Avaluma Test Client works with both LiveKit Cloud and self-hosted LiveKit servers, making it the most flexible option for any deployment.
1

Open the test client

Navigate to https://avaluma.ai/test-client in your browser.
2

Enter your LiveKit credentials

Fill in your LiveKit URL (e.g. wss://your-project.livekit.cloud), API Key, and API Secret from your .env.local file.
3

Enter the agent name

Type the AGENT_NAME configured in your docker-compose.yaml (e.g. agent-1).
4

Click Connect

Click Connect. The avatar video stream should appear within a few seconds as the agent joins the room and begins rendering.

​
Connect with the LiveKit Agent Playground

The LiveKit Agent Playground is available when you are using a LiveKit Cloud project and provides a one-click connection experience using your project’s stored credentials.
1

Open the playground

Navigate to https://agents-playground.livekit.io in your browser.
2

Select your project or enter credentials

Choose your LiveKit Cloud project from the dropdown, or manually enter your server URL, API key, and API secret.
3

Enter the agent name

Type the AGENT_NAME set in your agent’s docker-compose.yaml environment block (e.g. agent-1).
4

Click Connect

Click Connect to open a room. The agent will join automatically and the avatar video stream will begin.
If the agent does not respond after changing the agent name, reload the page and reconnect. The LiveKit Agent Playground caches the previous agent name in the session and may not dispatch to the correct worker until you reload.