Gemini CLI Telemetry in Beacon | Asymptote
What is Gemini CLI?
Gemini CLI support added local OTLP configuration, discovery, status reporting, and normalization for prompts, tools, MCP activity, files, and approvals.
Collection path: Opt-in local OTLP
Authoritative date: May 19, 2026 from v0.0.14 in the Beacon CLI changelog.
How Beacon reads Gemini CLI
Beacon manages Gemini settings when the gemini harness is included, pointing local OTLP telemetry at the Beacon collector and normalizing emitted activity into endpoint events.
The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.
Telemetry coverage
- Prompts and tool calls
- MCP activity
- File operations
- Approval-related events where emitted through OTLP
What you can do now
- Include Gemini CLI in endpoint harness configuration.
- Validate Gemini telemetry state through discovery and status commands.
- Forward Gemini activity with the rest of Beacon endpoint telemetry.
Get started
- Add gemini to the endpoint harness list, such as claude,codex,gemini.
- Run beacon endpoint install or repair.
- Confirm Gemini events in runtime.jsonl or the local dashboard.