Neura Market Logo

Telemetry in ClawHub CLI: Collection and Opt-Out

Learn when and what telemetry ClawHub CLI collects during skill and plugin installations, and how to disable it. This page is for users who want to understand or control their data.

Read this when

  • Working on telemetry / privacy controls
  • Questions about what data is collected

Telemetry

ClawHub sends minimal CLI telemetry to calculate overall skill and plugin installation numbers.

When telemetry is collected

Telemetry is only transmitted when:

  • You are signed in to the CLI.
  • You run clawhub install <slug>, or finish an authenticated openclaw plugins install clawhub:<package> installation.
  • Telemetry is not turned off (see “How to disable” below).

If you are not logged in, no data is sent.

What we collect

Once a skill or plugin is installed and its local install record is saved, the CLI fires a single best-effort install event.

The event contains:

  • The installed skill slug or the canonical plugin package name.
  • version: the installed version, if known.

What we do not collect

  • No directory paths or identifiers derived from directories.
  • No file contents.
  • No per-session logs, prompts, or other CLI output.

Install counts

For skills, ClawHub keeps track of:

  • installsAllTime: unique users who have reported at least one CLI install for that skill.
  • installsCurrent: unique users who have reported an install and have not removed their telemetry.

For plugins, ClawHub records the first successful install reported by each user and package. Repeated installs and updates refresh the stored version without raising the overall install count.

Transparency + user controls

Everyone sees only aggregated install counters.

Deleting your account also erases your telemetry data and removes its contribution from install counters.

How to disable telemetry

Set the environment variable:

export CLAWHUB_DISABLE_TELEMETRY=1

With this set, the CLI will not send install telemetry.