i've deployed the agent using LiveKit cloud. But i...
# ask-ai
c
i've deployed the agent using LiveKit cloud. But im unable to find the test URL. Where to find it?
✅ 1
t
Thanks for reaching out, temp. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I understand you’ve deployed an agent to LiveKit Cloud but can’t find the test URL. I can help you locate it. What to do: 1. Open the LiveKit Cloud console: https://cloud.livekit.io/ and go to your project. 2. In the project, open the Agents dashboard and select the deployed agent you want to test. 3. Click the Test Agent button in the top-right of the builder interface. That opens the LiveKit Cloud Sandbox test frontend and provides a public test URL you can use to interact with the agent. 4. If you don’t see Test Agent, open the agent’s dropdown menu and choose Regenerate test app — that will create the test frontend and make the test URL available. If that doesn’t surface a URL for you, please tell me: • The agent name (or project ID), and • Whether you see a Test Agent button or the Regenerate test app option in the builder. I’ll walk you through the next steps once you share that. Sources: Agent Builder | LiveKit Documentation
c
this is the project ID - p_1qnh85ugfs1 unfortunately i dont see it.
t
Thanks — I appreciate the project ID and that you can’t see the Test Agent option. I can help diagnose what’s going on. Before we dig deeper, please provide the following so I can narrow the cause quickly: • The agent name(s) in project
p_1qnh85ugfs1
and which one you deployed. • The deployment status shown for that agent in the Agents dashboard (for example: “Deployed”, “Draft”, or any error message). • Whether you can see the Agents list and the agent builder UI at all, and specifically whether the Test Agent button or Regenerate test app option appears in any dropdown. • Your account role on this project (owner, admin, collaborator, viewer). • A screenshot of the Agents dashboard or the agent builder page where you expect the Test Agent button (you can redact any sensitive info). • Browser and OS you’re using, and whether you’ve tried a different browser or an incognito/private window. Quick next steps I’ll take once you send those: • If the agent shows as not “Deployed,” I’ll walk you through redeploying. • If the agent is “Deployed” but the Test Agent button is missing, I’ll check whether it’s a permissions or UI-render issue and advise the exact UI steps to regenerate the test app. • If you share a screenshot, I can point to the precise menu or button to click. Send those details and I’ll guide you through the exact fix.
c
the status is deployed. this is the agent name - Cameron-243b
t
Thanks — I see project
p_1qnh85ugfs1
and the deployed agent
Cameron-243b
. I’ll help you get the test URL. Please try these targeted steps — I’ll walk you through checks that usually resolve the missing Test Agent button: 1. Confirm you’re in the right place ◦ Open https://cloud.livekit.io/ and select project
p_1qnh85ugfs1
. ◦ Go to the Agents dashboard and click the agent named Cameron-243b to open the builder. 1. Look for the Test Agent controls ◦ In the top-right of the agent builder you should normally see a Test Agent button. If it’s not visible, click the 3-dot (more) menu in that top-right area and look for Regenerate test app. 1. If neither option is visible, try these quick UI checks ◦ Reload the page and clear cache (or open an incognito/private window). ◦ Try a different browser (Chrome, Firefox, or Safari). ◦ Ensure your account role has sufficient permissions (owner/admin/collaborator). The Test Agent may not appear for view-only roles. 1. If the agent is marked “Deployed” but Test Agent still missing ◦ In the agent builder, open the 3-dot menu and run Regenerate test app if present. That recreates the sandbox frontend and will produce the public test URL. ◦ After regenerating, wait a minute and then refresh the Agents dashboard — the test frontend link will appear and open the LiveKit Cloud Sandbox. If none of the above surfaces the Test Agent or Regenerate option, please send: • A screenshot of the agent builder top-right area (you can redact sensitive info). • The role you have on the project (owner/admin/collaborator/viewer). • Which browser and OS you’re using. Send that and I’ll point exactly where the option should be or suggest the next fix.
c
see, it shows now deployment is complete and i dont see any test url button or regenerate app in the context menu.
t
Thanks — I can see the screenshots and that the agent shows as “Deployed” / “RUNNING” but the Test Agent / Regenerate test app options aren’t visible. I’ll help you get a working test URL or surface why the button is missing. Quick note about what I’m responding to: • You deployed agent Cameron-243b in project p_1qnh85ugfs1 and screenshots show deployment complete, but there’s no Test Agent button or Regenerate test app option in the UI. What to try next (fast checks) 1. Use the Live preview Start Call ◦ In your screenshot the right panel shows the Live preview with a large “START CALL” button. Click that button — it should open the sandbox test frontend (the same test URL you’re looking for). Try that and let me know whether it launches the test call UI or opens a new tab with a public URL. 1. Check the kebab menu again ◦ In the screenshot the three-dot menu is open. Look for these items there: View agent analytics, Show edit history, Download code, or Delete agent. If you don’t see Regenerate test app in that menu, proceed to the next checks. 1. Confirm your role/permissions ◦ Please tell me your project role (owner/admin/collaborator/viewer). The Test Agent / regenerate option may not be visible to view-only roles. 1. Try a different browser / private window ◦ Open the console in an incognito/private window or another browser and re-open the agent page. Some UI elements can be hidden by cached assets or extension interference. If the Start Call button did not give you a URL, please send me: • A short video or step-by-step result of what happens when you click START CALL (does nothing, opens a modal, opens a new tab, shows an error). • Your project role (owner/admin/collaborator/viewer). • The browser and OS you’re using. What I’ll do after that: • If START CALL opens the sandbox but no persistent public URL is shown, I’ll show how to copy the test URL from the sandbox or regenerate the test app via the correct menu path. • If nothing happens when you click START CALL or the regenerate option is missing and you have the correct role, I’ll run through the exact UI checks and next diagnostic steps with you. If you can try clicking START CALL now and tell me what happens (or share the behavior), I’ll guide the exact next step.
c
start call works, but no test URL
t
Thanks — good info. Since START CALL launches the sandbox but no test URL is visible, let’s extract the URL from that running session or confirm why a public test URL isn’t being shown. I’ll walk you through two straightforward options and a couple of checks. What I’m responding to: • You can start a live call with Cameron-243b (START CALL works) but you don’t see a public test URL or a Test Agent / Regenerate test app option. Option A — Get the sandbox URL opened by START CALL 1. After clicking START CALL, look at your browser address bar: ◦ If the sandbox opened in a new tab, the public test URL will be the page URL. Copy that URL and use it to share the test frontend. 1. If START CALL opened a modal or an in-page view: ◦ Right-click the page background and choose “Open in new tab” or “Open frame in new tab” (some browsers show that on embedded frames). ◦ Alternatively open Developer Tools (F12) → Network tab → then click START CALL again and look for a request that loads the sandbox frontend (look for a request whose response is HTML). Right-click that request → Open in new tab → copy the URL. Option B — Extract the session/test frontend URL from the browser console 1. With the START CALL live preview open, open Developer Tools (F12) → Console. 2. Search the console for logs that contain "sandbox", "test", "frontend", or a URL string — sometimes the frontend prints the test URL or a connect URL. 3. If you see a WebSocket or websocket-like URL (wss://) or an http(s) origin pointing to a sandbox domain, copy that origin; it’s often the test frontend base URL. Quick checks to confirm why you don’t see a visible Test URL • Role: Tell me your project role (owner/admin/collaborator/viewer). View-only roles may hide test/frontend management UI. • Popup/Blockers: Ensure no popup or content blocker is preventing the START CALL from opening a new tab. • Incognito/Other Browser: Try START CALL in an incognito window or another browser to confirm the behavior is consistent. If you prefer, send me either: • The browser and OS you’re using and whether START CALL opened a new tab or an embedded modal; or • A short screen recording/gif of clicking START CALL and what opens (you can redact sensitive info). What I’ll do after you reply: • If you paste the URL you find (or describe what you see in Network/Console), I’ll confirm whether it’s the correct public test frontend and how to use/share it. • If nothing usable appears, I’ll provide the next exact UI/console commands to recreate/regenerate the test frontend so you have a shareable URL. Try Option A first (check the address bar or open the loaded frame in a new tab) and tell me what you find — I’ll guide the next step. , with interactive elements