(expressive mode): hide and remove from examples#6370
Merged
Conversation
Remove the user-facing expressive surface while keeping the pipeline machinery internal and disabled: - drop the `expressive` param from AgentSession and Agent (and the Agent.expressive property) - drop the `expressive` field from AgentSessionOptions - stop exporting ExpressiveOptions and presets from livekit.agents.voice - AgentSession hardcodes an internal `_expressive = False`, which AgentActivity._resolve_expressive_options() now reads, so the markup/presets machinery stays intact but always resolves disabled - remove `expressive=presets.*` usage from the examples
theomonnom
approved these changes
Jul 9, 2026
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove the user-facing expressive surface while keeping the pipeline machinery internal and disabled:
expressiveparam from AgentSession and Agent (and the Agent.expressive property)expressivefield from AgentSessionOptions_expressive = False, which AgentActivity._resolve_expressive_options() now reads, so the markup/presets machinery stays intact but always resolves disabledexpressive=presets.*usage from the examples