[BUG] Missing toggles for web search, URL context for Gemini in Roo Code settings

[ElliotK-IB]

Problem (one or two sentences)

The docs for Google Gemini and Vertex AI both state that the settings should show options to toggle on/off advanced Gemini-specific features like web search and URL context.

However, neither of these options are available.

Screenshot of Roo Code Settings

Details

I primarily need Vertex AI and would especially like the enterpriseWebSearch tool enabled--but that could be another discussion.

Version: 3.50.5
System: WSL2 Ubuntu 24.04

Context (who is affected and when)

Happens to users who try to enable Gemini's native tools in Settings > Providers

Reproduction steps

1. Open Settings > Providers
2. Set 'API Provider' to 'GCP Vertex AI' (or 'Google Gemini')
3. Set Google Cloud Project ID and Google Cloud Region ('global')
4. Set 'Model Reasoning Effort'
5. Open 'Advanced settings'

Expected result

Advanced settings shows toggles for web search and URL context

Actual result

Advanced settings only shows 'Enable todo list tool', 'Use custom temperature', 'Rate limit' and 'Error & Repetition Limit'

Variations tried (optional)

API providers: GCP Vertex AI, Google Gemini
Model:

• gemini-3.1-pro-preview
• gemini-3-flash-preview
• gemini-3-pro-preview
• gemini-2.5-pro
• gemini-2.5-flash

App Version

3.50.5

API Provider (optional)

Google Vertex AI

Model Used (optional)

gemini-3-flash-preview

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's what I found:

Root Cause: The "Enable URL context" and "Enable Grounding with Google search" toggles were intentionally removed in PR #11253 (commit 2053de7b4), described as a "cleanup task requested by maintainers." That PR removed:

• enableUrlContext and enableGrounding fields from the provider settings schemas (packages/types/src/provider-settings.ts)
• The checkbox UI from both Gemini.tsx and Vertex.tsx components
• The tool injection logic in completePrompt for both providers
• Translation keys from all 18 locale files
• Tests were updated to assert these checkboxes are NOT present

The existing tests now explicitly verify checkbox-url-context and checkbox-grounding-search do NOT render.

Technical context: The Gemini API has a constraint where Google built-in tools (Grounding, URL Context) are mutually exclusive with function declarations. Since createMessage (the main chat flow) always uses function declarations for tool use, these features can only work in completePrompt (used for non-tool-use scenarios like summarization). The removal in #11253 also stripped the completePrompt integration.

Proposed implementation plan to restore these toggles:

1. packages/types/src/provider-settings.ts - Add enableUrlContext: z.boolean().optional() and enableGrounding: z.boolean().optional() back to both geminiSchema and vertexSchema

2. webview-ui/src/components/settings/providers/Gemini.tsx - Add two Checkbox components for "Enable URL context" and "Enable Grounding with Google search" with data-testid="checkbox-url-context" and data-testid="checkbox-grounding-search"

3. webview-ui/src/components/settings/providers/Vertex.tsx - Same two checkboxes as Gemini

4. src/api/providers/gemini.ts - In the completePrompt method, conditionally add googleSearch and urlContext tools to the GenerateContentConfig when the respective settings are enabled. Using the native @google/genai SDK, this means adding tools: [{ googleSearch: {} }] and/or tools: [{ urlContext: {} }] to the config

5. Translation keys - Restore urlContext and groundingSearch keys to webview-ui/src/i18n/locales/en/settings.json (and ideally all 18 locale files)

6. Tests - Update Gemini.spec.tsx and Vertex.spec.tsx to verify the checkboxes render, and update gemini-handler.spec.ts to verify completePrompt passes these tools when enabled

Important note: Since Grounding/URL Context are mutually exclusive with function declarations in the Gemini API, these features will only apply to the completePrompt path (summarization, etc.), not the main createMessage chat flow which requires function declarations for tool use.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.