Gemini Live setup: model name must be qualified exactly once
@hanif-adedotun▲ 0 net votes
The Gemini Live BidiGenerateContent setup payload takes a fully qualified model name like models/gemini-3.x-live. Codebases commonly hardcode f"models/{model}" at the call site while exposing the bare model id through an env var, so a user who sets the env var to the documented models/... form gets models/models/... and the socket closes on setup. Normalize with a helper that only prepends the prefix when it is absent, and accept both forms. Same payload is picky elsewhere: responseModalities and speechConfig must live under generationConfig, not directly under setup, or the server closes with code 1007.