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

Google plugin: the model does not stay silent after a tool returns `None` on Vertex AI

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

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

@aayushbaluni がすでに取り組んでいます。

2026年10月8日 から。

  • #7664 @aayushbaluni による — オープン

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
gcp, python
領域
ai

調査の方向性

Start with the Gemini-only scheduling: SILENT condition in livekit-plugins/livekit-plugins-google/livekit/plugins/google/utils.py (around lines 81-83) and realtime/realtime_api.py (around lines 729-745). The goal is to send scheduling on Vertex AI for a NON_BLOCKING tool that returns None. Run the linked repro_vertex_silent.py gist to confirm the model stays silent. A pull request (#7664) is already open for this, so check it before starting.

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

説明

bug
Bug Description

In LiveKit, a tool that returns None needs no reply. On Vertex AI, the model replies to it, even when the tool is NON_BLOCKING.

What I observed

I ran 10 trials for each cell on 2026-10-08, with Vertex AI in us-central1.

Model on Vertex AI BLOCKING NON_BLOCKING
gemini-3.8-live replied 10/10 replied 10/10
gemini-live-2.5-flash-native-audio replied 10/10 replied 10/10

What the plugin sends

The plugin keeps the model silent with scheduling: SILENT, but only on the Gemini API (utils.py, realtime_api.py):

API tool_behavior scheduling for a tool that returns None
Gemini API NON_BLOCKING SILENT
Gemini API BLOCKING, or not set not sent
Vertex AI any not sent

On Vertex AI, the plugin logs "pass tool_behavior=NON_BLOCKING to keep it silent" even for NON_BLOCKING tools.

Vertex AI supports scheduling now

The plugin skips Vertex AI because of #3784 (2025-11). In that issue, gemini-live-2.5-flash-preview-native-audio-09-2025 on Vertex AI rejected scheduling with 1007 Unknown name "scheduling". #3793 fixed it with the comment "vertexai currently doesn't support the scheduling parameter". #6785 then added scheduling: SILENT only on the Gemini API.

The model from #3784 is no longer available on Vertex AI. The Vertex AI documentation now lists scheduling (Asynchronous function calling). When the NON_BLOCKING tool response included scheduling: SILENT, both models above accepted it and stayed silent in 10 of 10 trials, and no session ended with an error.

Expected Behavior

On Vertex AI, the plugin sends scheduling: SILENT for a NON_BLOCKING tool that returns None, as on the Gemini API, and the model stays silent.

Reproduction Steps
1. Create `google.realtime.RealtimeModel(vertexai=True, model="gemini-3.8-live", tool_behavior=types.Behavior.NON_BLOCKING)`.
2. Give the agent a function tool that returns `None`.
3. Send a user message that makes the model call the tool.
4. The tool returns `None`. The plugin logs "a tool result wants no reply, but Gemini will answer it anyway; pass tool_behavior=NON_BLOCKING to keep it silent", and the model replies.

I used this script for the repeated trials in the description: `repro_vertex_silent.py` in https://gist.github.com/pokutuna/ff5a12222f44632d9fd8f5d7c722364f
Run it with: `uv run repro_vertex_silent.py`
Each API needs its own credentials. The script skips an API without them:
  Gemini API: `GOOGLE_API_KEY`
  Vertex AI:  `GOOGLE_CLOUD_PROJECT` and Application Default Credentials
Operating System

macOS 26

Models Used

Google RealtimeModel on Vertex AI: gemini-3.8-live, gemini-live-2.5-flash-native-audio

Package Versions
livekit-agents==1.8.5
livekit-plugins-google==1.8.5
google-genai==2.28.0
Session/Room/Call IDs

(None. I ran the script locally, without LiveKit Cloud. Each session has one user turn.)

Proposed Solution
Send `scheduling` on Vertex AI too, in the same way as on the Gemini API.
I can open a pull request for this.
Additional Context

What the proposed change affects

The proposed change only removes the Vertex AI condition from the plugin. Nothing changes on the Gemini API.

Case on Vertex AI Now With the change
NON_BLOCKING tool returns None no scheduling, the model replies scheduling: SILENT, the model stays silent
NON_BLOCKING tool returns a value no scheduling no change
BLOCKING, or tool_behavior not set no scheduling no change
the user sets tool_response_scheduling dropped, with a warning sent

gemini-3.8-live uses NON_BLOCKING by default, so with the default settings its tools that return None become silent. On Vertex AI, I tested only SILENT, not the other tool_response_scheduling values.

Notes

  • In each trial, the user gives one answer as text, and the model calls a tool. The tool returns None after 5 seconds, and the script watches for speech from the model for 15 seconds. The delay keeps out speech that some models make while a NON_BLOCKING tool runs.
  • Not tested: Vertex AI regions other than us-central1, and audio input.
  • A separate problem: the plugin also sends scheduling: SILENT to gemini-3.8-live-extended-thinking (Gemini API), because 3.8 models use NON_BLOCKING by default. This model does not support scheduling (model page), so the server closed the session with 1007 "Function response scheduling is not supported for this model." in 10 of 10 trials. The same script shows this when GOOGLE_API_KEY is set.
  • Related: #7302
Screenshots and Recordings

(None)

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

環境構築

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

はじめの一歩

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

livekit/agents のほかの issue

livekit/agents の issue をすべて見る

似ている issue

Python の issue をもっと見る

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

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