wooden-king-32027
05/28/2026, 1:54 PMtall-airline-16756
05/28/2026, 1:54 PMtall-airline-16756
05/28/2026, 1:54 PMroom_id, room, or the SDK context property) and a short code snippet.
Sources: Agent Console | LiveKit Documentation, with interactive elementswooden-king-32027
05/28/2026, 1:55 PMtall-airline-16756
05/28/2026, 1:55 PMroom_id, room, or JobContext.room) and a short code example.
Sources: Agent Console | LiveKit Documentation | Job lifecycle | LiveKit Documentation, with interactive elementswooden-king-32027
05/28/2026, 1:56 PMtall-airline-16756
05/28/2026, 1:56 PMctx (JobContext). You can read the room name with ctx.room.name. The docs show examples using ctx.room (e.g., ctx.room.name) for room access, and LiveKit logs include both Room name and Room ID by default.
I don’t have a confirmed property name for the room’s unique ID (e.g., ctx.room.id vs ctx.room.sid) in the sources I can see. Quick question so I give an exact snippet: do you need the human-readable room name or the unique room ID/SID? If you want, paste a short redacted sample of your ctx.room object and I’ll point to the exact field and a tiny code example.
Sources: How to Build a Background Observer for Voice AI Guardrails | LiveKit | How to Send Logs from the JavaScript SDK to Providers like Datadog, with interactive elements