Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Option to start a reply on time when caller noise began while the agent was thinking (1.6.6 behavior)

オープン
  • 何か問題がありますか？
#7,837 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
40/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
ai, audio-video-rtc

調査の方向性

Start in AgentActivity._reconcile_playout_pause, where the hold on a paused speech handle is decided, and in on_start_of_speech, which records the pause with agent_state. Then check generation._audio_forwarding_task to see where playback resumes. Done means a new InterruptionOptions flag that defaults to current behavior, and a test showing that with the flag off, a reply paused during thinking resumes at forwarding start. Confirm the design with maintainers before coding, since the issue proposes the setting but nobody has agreed to it.

索引モデルが issue の本文から書いたものです。

説明

Feature Type

Would make my life easier

Feature Description

An InterruptionOptions setting to start a reply's audio on time when caller noise began while the agent was thinking, as 1.6.6 did. For example hold_reply_while_user_speaking: bool = True; when false, _reconcile_playout_pause would resume at forwarding start.

What changed (1.6.6 → 1.8.6, unchanged in 1.8.7 and 2.0.0b1)

When VAD start-of-speech arrives while the agent is thinking, on_start_of_speech pauses the current speech handle. That is the same in both versions.

  • 1.6.6: generation._audio_forwarding_task began with audio_output.resume(), so the reply played as soon as its audio was ready.
  • 1.8.x: _reconcile_playout_pause keeps that pause ("a paused playout stays paused regardless of forwarding status"). The reply waits for VAD end of speech, which is the sound's length plus min_silence_duration. A sound of 0.5 s or more also counts as an interruption, so the reply then waits for false_interruption_timeout too.

Impact (telephony, Deepgram Flux with turn_detection="stt", interruption mode "vad")

Scripted VAD and STT through a real AgentSession. LLM first token after 0.7 s. First audio at 2.48 s with no noise:

Caller sound near reply start 1.6.6 first audio 1.8.6 first audio
none 2.48 s 2.48 s
0.1–0.3 s 2.48 s 3.05–3.25 s
0.6 s 2.48 s 5.35 s

On phone lines, breaths, line noise and short "mm" sounds near reply start are common. Each adds 0.6 s or more of dead air before the agent answers.

Workarounds / Alternatives
  • We currently monkeypatch AgentActivity._reconcile_playout_pause to call audio_output.resume() unconditionally, matching 1.6.6, and pin its source in a test so upgrades surface changes.
  • Setting false_interruption_timeout=None removes the hold, but also turns off resuming after a false interruption mid-reply, which we want to keep.
  • Making VAD less sensitive also changes endpointing and interruptions.
Additional Context

The setting could apply only to pauses recorded while the agent was thinking (_PausedSpeechInfo.agent_state == "thinking"). Interruptions during playback would keep today's behavior.

主要言語
Python
スター
14.6k
フォーク
3.9k
平均マージ
3日 1時間
マージ済み PR（30日）
166

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

livekit/agents のほかの issue

livekit/agents の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。