Skip to content

Conversation

@1egoman
Copy link
Contributor

@1egoman 1egoman commented Dec 8, 2025

  • @davidzhao had surfaced the need for agent participant identity for interfacing with with existing lower level apis (it looked like his use case was RPC calls)
  • Given this I think it makes sense to expose the agentParticipant's identity on the root useAgent() return value
  • When I got into this a bit further, I realized useParticipantInfo() was returning name + metadata alongside identity, so it seems like all three are probably equally important (especially since all three are exposed in TokenSourceFetchOptions)

@changeset-bot
Copy link

changeset-bot bot commented Dec 8, 2025

🦋 Changeset detected

Latest commit: 9f362b7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@livekit/components-react Patch
@livekit/component-example-next Patch
@livekit/components-js-docs Patch
@livekit/component-docs-storybook Patch
@livekit/components-docs-gen Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

size-limit report 📦

Path Size
LiveKitRoom only 6 KB (0%)
LiveKitRoom with VideoConference 32.46 KB (0%)
All exports 43.31 KB (+0.2% 🔺)

Copy link
Member

@davidzhao davidzhao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lg, just would suggest updating the comment

failureReasons: null;

/** The client's assigned identity, coming from the JWT token. */
identity: Participant['identity'];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it the agent's identity? or the end-user's identity? the comment seems to be indicating the latter. (i.e. client).

assuming it's the agent's, i'd recommend changing the comment to be clear.

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.

3 participants