Google’s two enterprise coding surfaces have very different governance shapes and need separate deployment pages. Gemini CLI is Claude-Code-shaped — native OpenTelemetry, an MDM-deployable system-settings file, plus a cloud-hosted Management Console that overrides local settings. Gemini Code Assist is an IDE plugin governed entirely on the Google Cloud API layer — Cloud Audit Logs (cloudaicompanion.googleapis.com), Configurable Gemini Code Assist logging for prompt+response capture, and VPC Service Controls at the perimeter.
Primary data planes
- Gemini CLI — native OTel + system-settings file. OTLP/gRPC or OTLP/HTTP exporter with logs, metrics, and traces. System settings live at
/Library/Application Support/GeminiCli/settings.json(macOS),C:\ProgramData\gemini-cli\settings.json(Windows),/etc/gemini-cli/settings.json(Linux). → Gemini CLI - Gemini Code Assist — Cloud-native audit and logging. Enable Cloud Audit Logs Data Access on
cloudaicompanion.googleapis.com; enable Configurable Code Assist logging into a Cloud Logging bucket; export sinks to Arrakis. No endpoint-side hook. → Gemini Code Assist
Naming note (Antigravity vs. Code Assist)
As of 2026-06-18 Google unified the individual and Google AI Pro/Ultra tiers of its coding tooling under a new Antigravity multi-agent platform, sunsetting the corresponding IDE Extension and Gemini CLI SKUs. The paid business SKUs — Gemini Code Assist Standard and Gemini Code Assist Enterprise — retain that name; this page covers them.
Where telemetry lands
All coding-telemetry paths on this page terminate at the Arrakis coding-telemetry ingest, which runs the shared detection rules (typosquatting, secret exposure, template injection, tool collision, and others). Whether telemetry arrives as native OTLP, a hook-emitted event, or an admin-API pull, it is normalized into the same event registry.
Pages in this section
- Gemini CLI — MDM-managed system settings, native OTel, Management Console overrides.
- Gemini Code Assist — Cloud Audit Logs, Configurable Logging, VPC-SC.