how do you properly end a call with an agent from agents-js? It should also have access to the room or will the room close by itself if only the user without the agent is still there? How does the client react to the agent leaving or the room closing?

Thanks for reaching out, Francisco. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

so if an user is still in the room and i dont close it from the server it'll never leave the room?

Good question — here's a clear answer. If a user remains connected in the room and you do not explicitly delete or close the room from the server, the room will stay open. In other words, the room will not automatically disappear simply because the agent left; any remaining participants keep the room alive until one of these happens: • The last participant (the user) leaves the room — then the room is closed after the configured departure timeout. • You explicitly delete the room (for example with

RoomServiceClient.deleteRoom()

). • You configured the agent/session to delete the room on shutdown by setting

delete_room_on_close: True

in

RoomOptions

/

RoomInputOptions

when ending the agent session. What to keep in mind for your app • If you want the room to end as soon as the agent leaves even when the user remains, enable

delete_room_on_close

or call

deleteRoom()

from your server when the agent shuts down. • If you want users to continue in the room without the agent (e.g., for post-call actions), leave the room open and handle agent departure on the client (listen for the

disconnected

event and update UI accordingly). If you want, I can show: • A short code snippet for setting

delete_room_on_close

, or • An example of listening for the

disconnected

event on the client to handle agent leave events. Which would you prefer? , with interactive elements

how do you listen for the disconnected event on the client? does it have delay from when the agent runs its shutdown?

You're asking how to listen for the

disconnected

event on the client and whether there's any delay between the agent calling

ctx.shutdown()

and the client receiving that event. I'll cover both and include a short client-side example. Listening for the disconnected event • The client SDK emits a

disconnected

room event when the client is disconnected from the room (this occurs when the agent leaves, when the room is deleted, or when the client itself loses connection). • To handle this, register an event listener on the Room (or the equivalent room object in your client SDK) and run your cleanup/UI logic when you receive

disconnected

. Example (pseudo/JS-style) • Register the handler after joining the room:

room.on('disconnected', (reason) => {
  // reason may describe why (e.g., 'server_closed', 'network')
  // Stop local media, show "call ended", navigate away, etc.
  console.log('Room disconnected:', reason);
  stopLocalTracks();
  showCallEndedUI();
});

Timing / delay between agent shutdown and client event • There can be a short, typically small delay between the agent calling

ctx.shutdown()

and clients receiving

disconnected

. This is because: ◦ The agent's session needs to close on the server, and then the room state/update is propagated to connected clients. ◦ If you explicitly delete the room (e.g.,

RoomServiceClient.deleteRoom()

or

delete_room_on_close: True

), the server removes participants which triggers immediate disconnection events to clients. ◦ If the agent simply disconnects but the room stays open for remaining participants, clients only see the agent leave (a participant-left event) rather than a full

disconnected

for the user —

disconnected

appears for a client when that client itself is disconnected or when the room is closed/deleted. • In practice: expect near-real-time delivery (usually under a second), but network latency and processing can add small delays. If you need guaranteed immediate force-disconnect behavior for remaining clients, delete the room from the server when the agent shuts down. What you should do in your client • Listen for both: ◦ Participant updates (to detect the agent leaving): e.g.,

participant-removed

or participant state change events. ◦ The

disconnected

event (to detect the room being closed or the client being disconnected). • Implement UI that handles both cases: ◦ Agent left but room still exists → show “agent has left” and allow user actions. ◦ Room deleted / client disconnected → show “call ended” and perform full cleanup. Would you like a concrete code sample for: • The exact client SDK you’re using (web/JS, React, or native), or • An example that listens for both participant removal and room

disconnected

and shows the UI flows?, with interactive elements