fix voice config

[dyi1]

Proposed changes

Voice chat is now always-on by default. The voiceChat field in SessionConfig has been narrowed from boolean | VoiceChatConfig to VoiceChatConfig only, and the SDK applies voiceChat: {} (microphone on, unmuted) when the field is omitted entirely. To start a session with the microphone muted, pass voiceChat: { defaultMuted: true }.

A normalizeSessionConfig shim handles callers still passing the old boolean form at runtime: voiceChat: true maps to {} and voiceChat: false maps to { defaultMuted: true }, both with a console.warn pointing to the replacement. The shim is marked for removal in 0.0.20.

The configureSession method no longer conditionally starts voice chat — it always calls voiceChat.start, relying on the normalized config. The redundant typeof voiceChat === "object" guard in the constructor was also removed.

All call sites in the demo and bg-removal apps have been updated to pass VoiceChatConfig objects instead of booleans, and the LiveAvatarSession and ElevenLabsAgentProvider prop types have been updated to match. Tests cover the new default-on behavior, defaultMuted, and both deprecated boolean migrations.

An AGENTS.md has been added to the SDK source documenting the config design rules (one type per field, no union shorthands, alphabetical field order, JSDoc on every field, and deprecation shim policy) to prevent the boolean-union pattern from being reintroduced.

Bumps the SDK to 0.0.19.

[dyi1]

• fix voice config #111 👈 (View in Graphite)
• Add auto keep alive functionality #110
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.