Telemetry & Privacy

How Termix uses telemetry, what data is collected, and where it goes

Telemetry is the core of what makes Termix useful. It’s also the thing people are most likely to have questions about. Here’s the full picture.

What Telemetry Means in Termix

When we say “telemetry,” we mean the signals that CLI agents emit about their own activity. These are OpenTelemetry (OTLP) log messages that agents like Claude Code, Codex, and Gemini CLI already support.

Termix runs a local OTLP receiver on port 4000 and configures the agents to send their logs there.

Where Does the Data Go?

Nowhere. It stays on your machine.

The telemetry flow is:

CLI Agent → localhost:4000 → Termix → your browser

There is no cloud component. Termix doesn’t have a backend service, doesn’t phone home, and doesn’t collect analytics. Everything runs locally.

What Data Does Termix Receive?

From OTLP logs, Termix extracts:

Data	Used For
Session ID	Enabling session resume
Timing of log events	Confirming the agent is connected

Termix does not read:

• Your prompts or what you type to the agent
• The agent’s full responses or generated code
• File contents or repository data
• API keys or credentials

What About Working/Idle Detection?

Working/idle status is not determined from telemetry content. Termix uses I/O heuristics:

• How many bytes per second the terminal is outputting
• How long the current burst of output has been going
• Whether there’s been silence for more than 2 seconds

This is purely based on byte rates — Termix doesn’t need to know what the agent is saying, just that it’s saying something.

What About the Message Preview?

The sidebar preview (last message from the agent) comes from reading the terminal’s output buffer — the same text you see in the terminal. This is local to your browser and is not sent anywhere.

Can I Disable Telemetry?

Yes. Per agent:

1. Open Settings > CLI Agents
2. Select the agent
3. Uncheck Telemetry

Without telemetry, Termix still works as a terminal multiplexer. You lose:

• Session resume (no session ID capture)
• Telemetry setup detection
• Slightly less accurate status detection for some agents

The I/O heuristics still provide working/idle detection even without telemetry.

Auto-Setup: What Changes on My System?

When you click “Configure automatically” for an agent, Termix writes to the agent’s config file:

Agent	File Modified	What’s Added
Codex	~/.codex/config.toml	[otel] section with OTLP endpoint
Gemini CLI	~/.gemini/settings.json	telemetry object with local endpoint
Claude Code	Nothing	Uses environment variables (no file changes)
OpenCode	~/.config/opencode/plugins/	Plugin file copied (one-time)

Disabling telemetry in Termix settings removes these additions.