Skip to content

Conversation

Regaddi
Copy link
Collaborator

@Regaddi Regaddi commented Sep 17, 2025

This PR implements handling for multi-participant sessions. The local participant and bot are still referenced via "local" and "bot". Remote participants are returned through the usePipecatClientParticipantIds hook (can include "local" and "bot", too). We keep track of the bot's participant id to correctly distinguish between bot and remote participant tracks.

I have already outlined the changes in the changelog:

Added

  • Multi-participant support: Full support for handling multiple participants in sessions
    • New usePipecatClientParticipant() hook to access individual participant data
    • New usePipecatClientParticipantIds() hook to get all participant IDs with filtering options
    • Support for both regular and screen share media tracks per participant

Changed

  • PipecatClientVideo component now requires participantId prop when participant is set to "remote"
  • Enhanced PipecatClientAudio component now renders audio for all participants automatically
  • Enhanced PipecatClientVideo component now supports remote participants
  • usePipecatClientMediaTrack() hook signature updated to support remote participants

@Regaddi Regaddi self-assigned this Sep 17, 2025
@Regaddi Regaddi force-pushed the cst/multi-participants branch from 70c60b1 to 8012b24 Compare September 17, 2025 12:38
@Regaddi Regaddi force-pushed the cst/multi-participants branch from 8012b24 to 5b9d2cc Compare September 17, 2025 12:41
@Regaddi Regaddi requested a review from filipi87 September 18, 2025 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant