Skip to main content

Telemetry

Rune reports a small amount of anonymous usage data so we can see which features and languages people actually use, and which platforms and versions need support. This page lists every field that leaves your machine, and how to stop all of it with one setting.

Telemetry is on by default. Everything below is sent over HTTPS to api.rune.build.

What Rune sends

There are exactly two reports.

Once per launch

A system report is sent when Rune starts:

FieldValue
Install identifierA random identifier generated the first time you run Rune. It is not derived from your hardware, your account, or anything else about you.
Reset flagWhether the install identifier appears to have been reset. See Your install identifier.
Session identifierA random identifier generated fresh on every launch.
Rune versionThe version of the running build.
Editor modemodal, standard, emacs, or exo.
Operating systemFor example darwin or linux.
ArchitectureFor example arm64 or x86_64.
Kernel release and versionThe kernel strings your operating system reports.
Host nameThe machine's network name.

Once an hour

A usage report is sent every hour, and once more when you quit Rune. Every counter is reset after a successful report, so each one covers only the period since the last report:

FieldValue
Session identifierThe same per-launch identifier as above.
Editor modemodal, standard, emacs, or exo.
Files opened, closed, edited, savedFour counts. Counts only, never which files.
Watched file changesHow many files changed on disk under a language server's watch.
Commands runHow many commands you ran.
LanguagesA count of files opened per language, for example go: 14, python: 3.

The language list is normalized before it is sent. Rune derives the language from the file type alone, discards the path, and reports anything it cannot confidently identify as other. Unusually long identifiers are treated the same way, and a single session reports at most 64 distinct languages.

What Rune never sends

Telemetry never includes:

  • File names, paths, or workspace locations.
  • File contents, or any fragment of them.
  • Terminal output, command arguments, or shell history.
  • Agent prompts, agent responses, or anything else you type.
  • Your source code, in any form.

Rune's AI agent talks directly to the model provider you configure. Prompts and code never pass through Unstable Build's servers.

Your account

When you are signed in, the usage report is sent with your account credentials attached, so reports can be associated with your subscription. When you are signed out, the report is sent without them.

Signing out does not turn telemetry off. Use the setting below.

Your install identifier

The install identifier lets us tell one installation apart from another without knowing who you are. Rune keeps a second copy of it outside your configuration directory so the identifier survives a reinstall. If the primary copy is gone while the second copy remains, Rune restores the identifier and sets the reset flag on its next report.

When telemetry is off, no install identifier is created, stored, or copied anywhere.

Turning telemetry off

Set telemetry.enabled to false in your Rune config:

telemetry:
enabled: false

Restart Rune for the change to take effect. From then on Rune sends no usage or system reports at all, and stops collecting the counters that would have gone into them. Nothing is queued for later and nothing is written to disk.

What this setting does not cover

Turning telemetry off does not silence the rest of Rune's network activity, because none of it is background reporting:

  • Crash reports. If Rune crashes, it asks on the next launch whether to send the report, and does nothing unless you agree. A crash report contains the stack trace and the tail of Rune's debug log, which can include workspace paths and file names. Decline it and the report stays on your machine.
  • Update checks. Rune checks for new releases shortly after startup and once a day after that. The check sends no data about you. Turn it off with upgrade.auto_check_enabled, described in Upgrades.
  • Signing in and package downloads. Authentication and language package installs are things you ask Rune to do.
  • AI providers. Agent traffic goes directly to the provider you configured, under that provider's own terms.
Ask Rune Agent