Skip to main content
Gemini CLI is Google’s CLI coding agent. Termix supports it with one-click telemetry setup.

​
Setup

1

Launch a Gemini CLI session

Click Gemini CLI in the session launcher. The session starts normally.
2

Configure telemetry

On first launch, Termix shows a setup toast: “Telemetry not configured for Gemini CLI”. Click Configure automatically.Termix adds a telemetry section to ~/.gemini/settings.json with the correct endpoint settings.
3

Restart the session

After configuration, click Restart Session on the toast. The new session will have telemetry active.
This is a one-time setup. All future Gemini CLI sessions will have telemetry enabled automatically.

​
What the Config Looks Like

Termix adds this to your ~/.gemini/settings.json: 
{
  "telemetry": {
    "enabled": true,
    "target": "local",
    "otlpEndpoint": "http://localhost:4000",
    "otlpProtocol": "http",
    "logPrompts": true
  }
}
You can also add this manually if you prefer.

​
Session Resume

Gemini CLI supports session resume. Termix captures the session ID from telemetry and uses gemini --resume <sessionId> to reconnect to previous sessions.

​
Disabling Telemetry

If you want to stop sending telemetry from Gemini CLI to Termix:
  1. Open Settings > CLI Agents > Gemini CLI
  2. Uncheck Telemetry
Termix will remove the telemetry section from your Gemini settings file.
If Gemini CLI releases a major update that changes its configuration or telemetry format, you may need to update Termix. Check for the latest version with npm update -g termix-cli.