Skip to content

Telemetry

SpecKit Companion counts how the extension is used, anonymously. The counts decide which assistants and features get worked on.

Set speckit.telemetry to false in Settings. Turning off VS Code’s own telemetry (telemetry.telemetryLevel) also turns it off. With either one off, nothing is sent.

  • Which assistant and which workflow you chose.
  • That a step was sent: specify, plan, tasks or implement.
  • That a spec was created, opened, completed or archived.
  • That the Specs view, a living spec, a steering file or the sample was opened, and that a living-spec drift or sync check ran.
  • That an install prompt was shown or clicked.
  • That the extension was installed, once.
  • The versions of the extension, VS Code and the Spec Kit CLI, your platform, how many specs the project has, whether the Companion Spec Kit extension is installed, and how four settings are set: the default workflow, the Activity panel, the install prompt and telemetry.

Events are tied to a random id for your VS Code install and a random id per spec. Neither is derived from you or from the spec.

Your prompts, file paths, spec names, capability names and the names of your own workflows.

Every event and its properties are listed in docs/telemetry.md in the repository.

Configuration lists the other speckit.* settings.