Gemini CLI

​

Runtime overview

Beacon supports Gemini CLI through opt-in local OTLP logs, traces, and metrics.

​

Prerequisites

Before enabling Gemini CLI telemetry, make sure:

• Gemini CLI is installed and available as the gemini executable for the user or managed endpoint.
• beacon endpoint install has run so the local collector, endpoint config, and runtime log path exist.
• The install explicitly includes Gemini, for example beacon endpoint install --harness claude,codex,gemini.
• No project settings or GEMINI_TELEMETRY_* environment variables override the user-level Beacon settings you expect to use.
• Your team has reviewed content handling and destination access for prompt telemetry.

​

Collection path

Gemini CLI exports local OpenTelemetry data to Beacon’s localhost collector when the gemini endpoint harness is enabled. Beacon maps Gemini prompts, tool calls, MCP activity, file operations, and approval-related events into normalized endpoint events.

​

Discovery and status

Beacon detects Gemini CLI through the gemini executable and ~/.gemini/settings.json. Use beacon endpoint discover or beacon endpoint status to confirm that Gemini CLI is present and configured.

​

Install or configuration support

Gemini CLI telemetry is opt-in. Run beacon endpoint install --harness claude,codex,gemini when you want Beacon to manage Gemini telemetry settings. Beacon writes local OTLP settings to ~/.gemini/settings.json, sets target to local, uses OTLP gRPC, enables collector mode, and removes outfile so telemetry flows to Beacon. Gemini CLI is not currently configured through Beacon’s hook adapter.

​

Telemetry coverage

​

Deployment notes

Project settings or GEMINI_TELEMETRY_* environment variables may override Beacon’s user-level Gemini config. For enterprise rollouts, add gemini to the endpoint harness list, for example claude,codex,gemini, when you want Beacon to manage ~/.gemini/settings.json for local OTLP collection. If a system collector is running while the CLI is reading the default per-user log, beacon endpoint status and the local dashboard surface a runtime-log source warning so you can tell where OTLP events are being written.

​

Related