Changelog entries for TTS context tracking

This commit is contained in:
filipi87
2026-02-10 11:37:21 -03:00
parent ad1bec4583
commit e00b98343e
5 changed files with 17 additions and 0 deletions

View File

@@ -0,0 +1,3 @@
- Added `append_to_context` parameter to `TTSSpeakFrame` for conditional LLM context addition.
- Allows fine-grained control over whether text should be added to conversation context
- Defaults to `True` to maintain backward compatibility

4
changelog/3584.added.md Normal file
View File

@@ -0,0 +1,4 @@
- Added TTS context tracking system with `context_id` field to trace audio generation through the pipeline.
- `TTSAudioRawFrame`, `TTSStartedFrame`, `TTSStoppedFrame` now include `context_id`
- `AggregatedTextFrame` and `TTSTextFrame` now include `context_id`
- Enables tracking which TTS request generated specific audio chunks

View File

@@ -0,0 +1,3 @@
- Simplified context aggregators to use `frame.append_to_context` flag instead of tracking internal state.
- Cleaner logic in `LLMResponseAggregator` and `LLMResponseUniversalAggregator`
- More consistent behavior across aggregator implementations

View File

@@ -0,0 +1,4 @@
- ⚠️ `TTSService.run_tts()` now requires a `context_id` parameter for context tracking.
- Custom TTS service implementations must update their `run_tts()` signature
- Before: `async def run_tts(self, text: str) -> AsyncGenerator[Frame, None]:`
- After: `async def run_tts(self, text: str, context_id: str) -> AsyncGenerator[Frame, None]:`

View File

@@ -0,0 +1,3 @@
- Updated all 30+ TTS service implementations to support context tracking with `context_id`.
- Services now generate and propagate context IDs through TTS frames
- Enables end-to-end tracing of TTS requests through the pipeline