ClawHub CLI Telemetry: Collected Data and Opt-Out Guide

Telemetry

ClawHub collects minimal command-line telemetry to determine aggregate counts of skill and plugin installations.

When telemetry is collected

Telemetry transmission occurs only under these conditions:

• Your CLI session is authenticated.
• You execute clawhub install <slug> or finish an authenticated openclaw plugins install clawhub:<package> installation.
• Telemetry remains enabled (refer to the “How to disable” section below).

When you are unauthenticated, no data is transmitted.

What we collect

Once a skill or plugin finishes installing and its local installation record is saved, the CLI transmits a single best-effort installation event.

That event contains:

• The slug of the installed skill or the canonical package name of the plugin.
• version: the version that was installed, if it is known.

What we do not collect

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

Install counts

For skills, ClawHub tracks:

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

For plugins, ClawHub records the first successful installation reported per user and package. Repeated installations and version updates refresh the recorded version without raising the aggregate installation count.

Transparency + user controls

All users see only aggregated installation counters.

If you delete your account, your telemetry data is removed and its contribution is subtracted from the installation counters.

How to disable telemetry

Configure the environment variable:

export CLAWHUB_DISABLE_TELEMETRY=1

When this variable is set, the CLI stops sending installation telemetry.