Skip to content

Session api use - #101

Draft
MaxHeimbrock wants to merge 7 commits into
mainfrom
max/session-api-use
Draft

MaxHeimbrock wants to merge 7 commits into
mainfrom
max/session-api-use

Conversation

@MaxHeimbrock

Copy link
Copy Markdown
Contributor

Introduces an agent window to use the new Rust session api developed in livekit/rust-sdks#1593

livekit 0.10 renames StreamTextOptions / StreamByteOptions to
SendTextOptions / SendByteOptions; the rest of the group moves to the
versions published alongside it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
MaxHeimbrock and others added 5 commits October 29, 2026 14:14
- StatusBar takes the room plus an optional detail badge and reconnect
  hint, and shows "Reconnecting..." during a reconnect; AgentStatusBar
  is gone and ConnectionButton is private again
- Auth replaces AgentAuth; LocalTokenSource names its room or picks a
  fresh one per fetch, so the connect form builds one enum for both modes
- Both settings structs carry e2ee_key: Option<String>, turned into
  E2eeOptions by one e2ee_options helper used by both services
- Remove AgentEvent::Messages, RoomNameField, the launcher's unused
  minimum size and the push_id around each chat message; for_agent uses
  struct update syntax
- Document the agent -> room widget reuse, the RoomContext rule and why
  TrackCmd::apply must run on the Tokio runtime
- Agent dispatch on room joins is intentional: README feature line,
  tooltip, and agent_metadata trimmed like agent_name

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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