Skip to content

docs: say which speaking timestamp gives turn completion order - #7984

Closed
u9g wants to merge 1 commit into
mainfrom
jason/sort-transcript-by-stopped-speaking
Closed

u9g wants to merge 1 commit into
mainfrom
jason/sort-transcript-by-stopped-speaking

Conversation

@u9g

@u9g u9g commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

For a user ChatMessage, metrics.started_speaking_at is the start of the whole user turn. A turn can span several VAD segments and stays open across a false-interruption resume, because STT can still return words for audio heard before the resume. So a turn's start can come before agent speech that played before the turn committed. Transcripts sorted by started_speaking_at then place the user's reply ahead of the agent line it answers (#7063).

This is expected behavior, so this PR documents it on MetricsReport.started_speaking_at and points readers to stopped_speaking_at for the order in which turns completed. To ignore speech such as a backchannel, filter STT events on SpeechEvent.speech_end_time, as adaptive interruption does.

Docstring only; no behavior change.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔍 Devin Review: 1 flag

Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

@u9g u9g closed this Oct 20, 2026
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