`lk app create --template agent-starter-react` is ...
# ask-ai
r
lk app create --template agent-starter-react
is not creating a sandbox It giving this error
template not found: agent-starter-react
t
Thanks for reaching out, Kamran. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The error
template not found: agent-starter-react
occurs because the template name
agent-starter-react
is not registered in the LiveKit CLI system. The correct template name for this repository is
voice-assistant-frontend
. To resolve this issue, use the following command instead:
Copy code
lk app create --template voice-assistant-frontend
This will create the sandbox using the correct template. If you'd like to see a list of all available templates, you can run:
Copy code
lk app create
Or use:
Copy code
lk app list-templates
Let me know if you need further assistance! Sources: README.md | Bootstrapping an application | LiveKit Docs | cmd/lk/app.go
r
getting this error -
error sending preconnect buffer {}
and the agent is not joining the room
t
Hey there! I totally understand how frustrating this
error sending preconnect buffer {}
can be. Let me break down what's happening in a way that makes sense and help you troubleshoot. What Might Be Going Wrong • Agent Timeout: Think of it like waiting for a friend who's running late - the system gives up after 10 seconds if no agent shows up. • Streaming Failures: Sometimes the audio data just gets a bit stuck and can't find its way through. • Agent Connection Issues: It's like trying to introduce two people at the wrong moment - timing is everything! • Buffer Data Issues: Missing some key information can be like trying to send a letter without an address. Let's Fix This Together 1. Timing is Key: Make sure your RoomIO gets started before connecting - it's like warming up before a workout. 2. Agent Check-In: Double-check that your agents are ready and can join rooms without any hiccups. 3. Network Love: Give your network some TLC and make sure it's stable and strong. 4. Buffer Details Matter: Dot your i's and cross your t's by ensuring all those important attributes are in place. Need a hand working through this? I'm here for you - just ask! Sources: livekit-agents/livekit/agents/voice/room_io/_pre_connect_audio.py | livekit-android-sdk/src/main/java/io/livekit/android/audio/PreconnectAudioB... | src/room/participant/LocalParticipant.ts | Sources/LiveKit/Core/Room+PreConnect.swift
r
what should be this parameter
Enter NEXT_PUBLIC_APP_CONFIG_ENDPOINT
t
Hey there! Let me break down the
NEXT_PUBLIC_APP_CONFIG_ENDPOINT
for you in a friendly way. Think of this as a cool trick for dynamically grabbing your app's settings. What's the deal? • Imagine being able to update your app's configuration without changing the code - that's exactly what this does! • It's super handy in LiveKit agent starter examples, giving you flexibility in managing your settings. Here's what you'll want to know: • This parameter is basically a special URL that: ◦ Welcomes GET requests with open arms ◦ Looks for an
X-Sandbox-ID
header (think of it like a secret handshake) ◦ Responds with a JSON configuration that fits the
SandboxConfig
format • Pro tip: It works best when you pair it with the
SANDBOX_ID
environment variable. Don't worry if something goes wrong - your app is smart and will just use default settings if the fetch doesn't work out. Need help setting this up? I'm all ears! Just give me a shout if you have any questions. Sources: .env.example
r
can it be any URL I want?
t
I don't have the answer you're looking for. You could also try asking your question: • in one of the other Slack channels or • to https://deepwiki.com/livekit/livekit_composite which is trained on all LiveKit source code If you find the answer, please post it here to help others!