Telemetry

What is sent

• the app version, operating system, CPU type and core count, and time zone
• whether a session ran in OmO Desktop or the command line
• which provider and model ran, when they are ones OmO ships; anything else is sent as custom
• rough sizes instead of exact numbers, such as a prompt length bucket or a memory size bucket
• token counts and cost for each turn and each delegated task
• which built-in skills, agents and features were used, and whether a message used a keyword
• crash reports: which part of OmO stopped, its version, and how long it had been running

What is never sent

• your prompts or the model's replies
• code, diffs, file names, file paths or folder names
• repository, branch or project names
• commands you ran, logs, or error messages
• account names, emails or keys
• screenshots, window titles or typed text from computer use
• the names of your own skills, providers or models

How you are counted

OmO creates a random install id on your computer and stores it there. It is not built from your name, hardware or accounts. Each computer is also identified by a one-way hash of its name; the name itself is never sent. Session ids are scrambled on your computer before they are sent, so sessions can't be matched across machines. No personal profile is built. The service that receives the data may work out an approximate country from the connection.

Turn it off

In OmO Desktop, choose Turn telemetry off when the telemetry notice first appears.

Anywhere, add this to ~/.omo/omo.jsonc:

{
  "telemetry": { "enabled": false }
}

Setting DO_NOT_TRACK=1 or OMO_DISABLE_POSTHOG=1 in your environment also turns it off. Turning telemetry off stops all of it, including crash reports.

The full list

Every event and every value OmO can send is listed in the telemetry reference. A test fails if that list and the code disagree.