How and why is there no option to update maxParticipants ? Why can’t we do increase maxParticipants after room creation as needed like this: roomServiceClient.updateRoomConfig({ maxParticipants: 30 })
Can/will this be added? In my app I want to allow users to change maxParticipants as needed, ofcourse it can only be more >= current participant count.
@PodoTip maxParticipants is a create-time field, not a mutable one. It is set on CreateRoom (livekit_room.proto#L90), and the RoomService API has no RPC that changes it afterward. The only room-level mutation is UpdateRoomMetadata, whose request carries just room and metadata (UpdateRoomMetadataRequest). So updateRoomConfig({ maxParticipants }) does not exist because there is no such RPC behind it.
The practical approach is to set the ceiling at creation, before participants join, by explicitly creating the room instead of letting it auto-create with defaults:
For a room that is already live there is no in-place update, so give it enough headroom at creation, or enforce a lower soft limit in your own app logic and raise it there. For changing it dynamically as a first-class feature, there is no existing request on the repos.
Just to clarify, by default there will be no limit on the max participants.
There are no plans to add this to the roadmap (I haven’t heard this requirement before), but if it’s something that would help your users, please consider raising a PR for this.