Thanks — great question. You're looking at

MoveParticipant

in the open-source server and asking whether participants can be moved in self‑hosted LiveKit or only in LiveKit Cloud, and whether there's a workaround. Short answer: MoveParticipant is not implemented in the open‑source/self‑hosted LiveKit server. That API is available only in LiveKit Cloud. Workarounds you can consider: • Use SIP transfer flows (e.g.,

TransferSIPParticipant

/

CreateSIPParticipant

) to route participants through a SIP gateway and recreate sessions in another room. • Implement custom logic in your application: create a new participant/session in the target room, signal the client to connect to that room, and tear down the original connection to emulate a “move.” • Orchestrate a warm/handoff by relaying media or signaling between rooms at the application layer (requires custom state and reconnection handling). If you tell me your use case (voice vs. full AV, need for seamless/zero‑gap transfer, number of participants), I can recommend the best workaround and sketch a concrete flow. Sources: The Human-in-the-Loop (HITL) Pattern for Voice Agents | LiveKit, with interactive elements