Thanks — I hear you: the Playground no longer accepts a raw wss+token flow and now opens the Agent Console, and your local dev agent no longer shows speaker/agent transcripts. I can help troubleshoot both. Quick facts and why this changed • The browser-based Agent Console replaced the older Sandbox/Playground flow and is now the primary testing/debug UI. It provides a unified view (audio, events, transcripts, metrics) instead of a simple wss+token connect flow. (If you preferred the old direct connect, that direct Playground flow is no longer the primary path.) What to check so your local dev agent shows transcripts 1. Agent SDK version ◦ Ensure your agent uses Agents SDK >= 1.5.2 (Python) or >= 1.2.4 (Node) — Agent Console features require recent SDK versions. 1. Agent run mode ◦ For local dev use

dev

mode (example commands:

uv run agent.py dev

for Python or

tsx agent.ts dev

for Node) so the agent registers as a worker visible to the Console. 1. Agent Console config ◦ Open the Agent Console in the Cloud dashboard, set the Agent name in the config panel, then click Save and start session to begin a session that shows real-time transcripts and audio. 1. Transcription stream subscription ◦ The frontend needs to subscribe to the

lk.transcription

text stream. Transcriptions are published on that topic by default when

text_output=True

. 1. AgentSession / output options ◦ Confirm your agent uses

AgentSession

with text outputs enabled (default). In Python this is `text_output=True`; in Node check

outputOptions

. If disabled, transcripts won’t be emitted. 1. Environment & auth ◦ When running locally, ensure

LIVEKIT_API_KEY

/

LIVEKIT_API_SECRET

and any project IDs match the Console/project you’re opening to avoid authentication/registration mismatch. If transcripts still don’t appear • Verify the agent console shows the agent as “registered worker” in your agent logs. • Check the Console’s Events view for

conversation_item_added

or

lk.transcription

events (these indicate transcriptions are being emitted). • If you’re running the agent in terminal-only console mode, use

uv run agent.py console

for local text/audio debugging without the web Console. If you want, tell me: • Which SDK (Python or Node) and SDK version you’re using, • The exact command you run to start the agent, • Whether the Agent Console shows the agent as registered. With those I’ll give targeted next steps. Sources: Build Your First AI Voice Agent in Python: Complete Tutorial | LiveKit | Text and transcriptions | LiveKit Documentation | Debug voice agents in real time with Agent Console | LiveKit | Troubleshooting 401 Unauthorized and Token Errors | LiveKit, with interactive elements