Usage statistics

See what anonymous usage statistics Meshy DCC Core sends, what it never sends, and how to turn them off.

Overview

Once a day, the Meshy DCC Core local service sends one anonymous, aggregate report to Meshy's product analytics. From version 0.2.4, the same report goes to two analytics services while Meshy moves between them. Meshy uses it to see which apps, connectors, and skills people use, and where tool calls fail.

The first meshy-dcc command you run prints a one-time notice. The window shows a banner until you click OK or Turn off. Both say what Meshy DCC Core sends and how to turn it off.

What Meshy DCC Core sends

The report holds counts and versions, never what you work on:

  • The versions of meshy-dcc and of the local service, and your operating system and CPU type.
  • The connectors you installed, with their versions.
  • The apps that are open when the report is made, with each app's major version (for example, Blender 4) and the number of open instances.
  • The tool calls of the day, counted for each app, skill, and outcome. The outcome is ok, error, timeout, or unknown. The report gives the median and 95th-percentile time as a range, such as 1-5s.
  • The name of a skill, only for a skill that came with a connector or from the Meshy marketplace. Every other skill, including the ones you write, is reported as custom.
  • The number of searches and of bug reports you sent, the kinds of agents that have the skill installed (for example, claude-code), and whether you opened the window.

Each report carries a random install ID that isn't tied to your Meshy account. The request is an ordinary web request, so your IP address reaches the analytics services as its source. Meshy DCC Core doesn't put an IP address, location, or person profile in the report. One of the services records a city and country derived from the request's IP address.

What it never sends

Meshy DCC Core never sends the following:

  • Tool arguments and outputs.
  • File paths.
  • Project, scene, and instance names.
  • Instance and request IDs.
  • Prompts and search queries.
  • Computer and user names.
  • Your Meshy account data.

Preview the next report

To see the exact report that Meshy DCC Core sends next, run:

meshy-dcc telemetry preview

The command prints the report and sends nothing. To check whether usage statistics are on, run meshy-dcc telemetry status.

For every field in the report, see Usage telemetry on GitHub.

Turn off usage statistics

To turn off usage statistics, do one of the following:

  • Run meshy-dcc telemetry off.
  • In the window, go to Settings and turn off Send anonymous usage statistics.
  • Set the DO_NOT_TRACK=1 environment variable.
  • Set the MESHY_DCC_TELEMETRY=0 environment variable.

Meshy DCC Core also sends nothing in continuous integration (CI) environments.

Turning usage statistics off deletes the counts and any report that isn't sent yet. After you set an environment variable, run meshy-dcc gateway restart so the local service reads it. To turn usage statistics on again, run meshy-dcc telemetry on.