Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix [Voice] Privacy & Compliance UX Warning [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25491•Fetched 2026-04-16 07:05:47
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
Abhijit-2592Abhijit-2592
Participants
Abhijit-2592Abhijit-2592
Timeline (top)
labeled ×4cross-referenced ×1

When using the Cloud/Gemini Live backend, voice recordings are sent to the Gemini API endpoint. This might create a mixed compliance scenario for enterprise users. We should add a UX warning to clarify data privacy and handling when cloud transcription is enabled.

Root Cause

When using the Cloud/Gemini Live backend, voice recordings are sent to the Gemini API endpoint. This might create a mixed compliance scenario for enterprise users. We should add a UX warning to clarify data privacy and handling when cloud transcription is enabled.

PR fix notes

PR #25519: fix: improve voice model selection flow

Description (problem / solution / changelog)

Addresses #24591 and #25492

Also addresses #25491.

Summary

  • show a one-time Gemini Live cloud-processing notice before first-time selection
  • persist the acknowledgement in settings so repeat selections skip the notice
  • close the voice model dialog immediately after successful Gemini Live selection
  • close the voice model dialog immediately after selecting an installed Whisper model
  • keep the dialog open while downloading a Whisper model, then close it after success
  • make Esc return to backend selection from the Gemini Live notice and Whisper model list

Note

  • this branch was originally based on the earlier voice-mode branch associated with #24174, so the PR commit history may show prior voice-related commits that are not part of the intended review scope
  • the intended review scope for this PR is the /voice-model dialog flow change described above

Testing

  • npx vitest run packages/cli/src/ui/components/VoiceModelDialog.test.tsx --reporter=basic

Changed files

  • .gemini/settings.json (modified, +2/-1)
  • docs/cli/settings.md (modified, +10/-0)
  • docs/reference/configuration.md (modified, +28/-0)
  • docs/reference/keyboard-shortcuts.md (modified, +1/-0)
  • integration-tests/voice-mode.test.ts (added, +76/-0)
  • packages/cli/src/config/config.ts (modified, +1/-0)
  • packages/cli/src/config/settingsSchema.ts (modified, +89/-0)
  • packages/cli/src/services/BuiltinCommandLoader.test.ts (modified, +2/-0)
  • packages/cli/src/services/BuiltinCommandLoader.ts (modified, +5/-0)
  • packages/cli/src/test-utils/render.tsx (modified, +3/-0)
  • packages/cli/src/ui/AppContainer.tsx (modified, +24/-0)
  • packages/cli/src/ui/commands/types.ts (modified, +2/-0)
  • packages/cli/src/ui/commands/voiceCommand.ts (added, +18/-0)
  • packages/cli/src/ui/commands/voiceModelCommand.ts (added, +19/-0)
  • packages/cli/src/ui/components/DialogManager.tsx (modified, +4/-0)
  • packages/cli/src/ui/components/InputPrompt.test.tsx (modified, +407/-0)
  • packages/cli/src/ui/components/InputPrompt.tsx (modified, +388/-14)
  • packages/cli/src/ui/components/VoiceModelDialog.test.tsx (added, +241/-0)
  • packages/cli/src/ui/components/VoiceModelDialog.tsx (added, +298/-0)
  • packages/cli/src/ui/components/shared/CircularProgress.tsx (added, +47/-0)
  • packages/cli/src/ui/contexts/UIActionsContext.tsx (modified, +3/-0)
  • packages/cli/src/ui/contexts/UIStateContext.tsx (modified, +2/-0)
  • packages/cli/src/ui/hooks/slashCommandProcessor.test.tsx (modified, +2/-0)
  • packages/cli/src/ui/hooks/slashCommandProcessor.ts (modified, +6/-0)
  • packages/cli/src/ui/hooks/useVoiceModelCommand.ts (added, +31/-0)
  • packages/cli/src/ui/key/keyBindings.ts (modified, +8/-3)
  • packages/cli/src/ui/noninteractive/nonInteractiveUi.ts (modified, +1/-0)
  • packages/core/src/config/config.ts (modified, +7/-0)
  • packages/core/src/index.ts (modified, +9/-0)
  • packages/core/src/utils/binaryCheck.ts (added, +14/-0)
  • packages/core/src/voice/audioRecorder.ts (added, +102/-0)
  • packages/core/src/voice/geminiLiveTranscriptionProvider.ts (added, +182/-0)
  • packages/core/src/voice/transcriptionFactory.ts (added, +41/-0)
  • packages/core/src/voice/transcriptionProvider.ts (added, +33/-0)
  • packages/core/src/voice/whisperModelManager.ts (added, +86/-0)
  • packages/core/src/voice/whisperTranscriptionProvider.test.ts (added, +31/-0)
  • packages/core/src/voice/whisperTranscriptionProvider.ts (added, +170/-0)
  • schemas/settings.schema.json (modified, +60/-0)
RAW_BUFFERClick to expand / collapse

Description

When using the Cloud/Gemini Live backend, voice recordings are sent to the Gemini API endpoint. This might create a mixed compliance scenario for enterprise users. We should add a UX warning to clarify data privacy and handling when cloud transcription is enabled.

Requirements

  • Add a warning/notice in the settings or upon first enabling the Gemini Live backend detailing the data flow.

Epic: #24175

extent analysis

TL;DR

Add a clear UX warning in the settings or when enabling the Gemini Live backend to inform users about potential data privacy and handling concerns.

Guidance

  • Identify the specific location for the warning, such as the settings page or a popup when the Gemini Live backend is first enabled, to ensure it is prominently displayed to users.
  • Determine the exact wording of the warning to accurately convey the data flow and potential compliance implications for enterprise users.
  • Consider adding a link to a privacy policy or additional resources for users who want more information about data handling and compliance.
  • Review the design of the warning to ensure it is noticeable and easy to understand, without being overly intrusive or disruptive to the user experience.

Example

No code snippet is provided as the issue focuses on adding a UX warning, which is more related to design and user interface rather than code implementation.

Notes

The solution should be tailored to the specific requirements and design of the application, ensuring that the warning is effective in communicating the necessary information without causing undue alarm or confusion.

Recommendation

Apply workaround: Add a UX warning to inform users about data privacy and handling when cloud transcription is enabled, as this directly addresses the identified issue and provides transparency to users about how their data is being handled.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING