Skip to main content
Skybridge collects anonymous usage telemetry to understand how the framework is used and where to improve it. It comes from two places: the CLI when you run skybridge dev, build, or start, and the server runtime when a Skybridge-powered MCP server handles a tools/call. Telemetry is optional, and the same controls turn off both.
We collect only aggregate usage data. We never collect personal information, source code, file contents, tool names, arguments, or results, end-user prompts, secrets, or any other sensitive data.

​
What we collect

​
CLI commands

Running a CLI command sends:

​
Server tool calls

Every tools/call increments one anonymous counter so we can measure aggregate production usage. The only data attached is the runtime version, as a tag: Unlike the CLI, this carries no machine or session ID. Development builds emit nothing.

​
Why we collect it

  • See which commands are used and where developers spend time
  • Surface the errors developers hit most
  • Decide which platforms and Node versions to support
  • Measure production adoption and which versions stay in active use

​
How to opt out

Preferences are per-machine. On your own machine, use the CLI; on CI runners and deployed servers, use an environment variable.

​
Configuration file

~/.skybridge/config.json stores settings per-machine:
It is created on the first CLI run with telemetry.enabled set to true. Set it to false to opt out.
In CI (GitHub Actions, GitLab CI, Jenkins), telemetry is enabled by default and the machine ID is set to the CI provider name, for example GitHub Actions.

​
CLI

All three read and write ~/.skybridge/config.json.

​
Environment variables

Environment variables take precedence over the config file. With either set, telemetry is off regardless of the config file, or of whether one exists at all.

​
Debug mode

To see the CLI telemetry payload without sending it:
It prints the event to stderr instead of sending it. Debug mode is CLI-only: the runtime counter carries nothing beyond the version, so there is nothing to inspect.

​
Data handling

CLI events go to PostHog, stored on its US servers. Events are anonymized, retained in aggregate for product analytics, and cannot be linked to a user. Tool-call events are emitted as a DogStatsD counter over UDP, fire-and-forget so they never block tool execution, and received by a Skybridge-operated Vector instance. Only per-version counters are stored, with no per-event record, so individual calls cannot be linked to a server, project, or user.