Skip to content
OpenWaggle

Usage statistics fields

Every event and field in OpenWaggle's anonymous usage statistics and error reports, with the limits the app and the endpoint apply.

This page lists every event, field and value that OpenWaggle’s anonymous usage statistics and error reports can contain, and the limits on them. The statistics endpoint rejects any event, field or value that is not on this page. Usage statistics and error reports explains why OpenWaggle sends them and how to turn them off.

Fields on every event

FieldValues
versionApp version, such as 1.0.0
build_channelChannel of the build you run: stable, beta, rc or alpha
update_channelUpdate channel you follow: stable, beta or alpha
osdarwin for macOS, win32 for Windows, or linux
archCPU architecture: x64 or arm64
dayUTC date, such as 2026-10-02. Never a time of day
countryTwo-letter country code, or XX when Cloudflare cannot tell. The endpoint adds it from the request and then drops your IP address. The app never sends it

version and previous_version must be release versions, such as 1.2.3 or 1.2.3-beta.4, at most 64 characters. The only suffixes are -alpha.N, -beta.N and -rc.N. The endpoint rejects any other shape.

Install events

EventWhen the app sends itFields
install.newOnce, with a new install’s first reportNone
install.activeAt most once per UTC day, only on a day with at least one runSee install.active fields
install.onboardingOnce, after a new install’s first day endsprovider_within_first_day, run_within_first_day, project_within_first_day
app.openedEach time the app opensNone
update.installedThe first time a higher version runsprevious_version

The three onboarding fields are true or false. The app works them out on your machine. Each says whether the install connected a provider, started a run, or opened a project during its first day.

A downgrade, or a channel switch that installs an older build, does not send update.installed.

install.active fields

FieldValues
first_this_weektrue on the install’s first active day of that week
first_this_monthtrue on the install’s first active day of that month
install_age0-7d, 8-30d, 31-90d, 91-365d or >365d
entry_pointsWhere that day’s runs started: any of app (the desktop app), cli (terminal commands) and agent (runs another agent started)
Feature flagstrue for each daily feature flag the install used that day
mcp_serversCatalog MCP servers whose tools the agent called that day, otherwise custom
skillsBuilt-in skills used that day, otherwise custom
extensions_enabledNumber of enabled extensions as a range: 0, 1, 2-5 or >5. Never their names

The app works out first_this_week and first_this_month on your machine, so the maintainer can count weekly and monthly active installs without an install ID.

The endpoint stores entry_points as one combined value, in the order app, cli, agent: for example app+cli, app+agent, cli+agent or app+cli+agent. The totals never show how many installs used more than one.

The app sends a feature flag, mcp_servers and skills only when they are true or not empty.

Run events

The app sends run.finished when a run ends.

FieldValues
entry_pointWhere the run started: app, cli or agent
providerProvider ID from Pi’s built-in catalog, such as anthropic, otherwise custom
modelModel ID from that provider’s built-in catalog, such as claude-sonnet-4-5, otherwise custom
thinking_leveloff, minimal, low, medium, high, xhigh or max
access_modeask-for-approval or yolo
waggletrue if the run was part of a Waggle conversation
resultcompleted, failed or interrupted
duration_sRun length in whole seconds, from 0 to 604,800 (one week)
input_tokensInput token total for the run, from 0 to 1,000,000,000,000
output_tokensOutput token total for the run, from 0 to 1,000,000,000,000

A provider outside the catalog makes both provider and model custom.

access_mode is the mode in force when the run last asked for approval. A run that never asked reports the mode it started under: its own override, its session’s mode, the project default, or the global default, limited by the session’s ceiling. A project config that cannot be read counts as ask-for-approval.

The app sends run.compacted when it compacts a conversation’s context. Its one field, mechanism, is native when the model compacts its own context, or fallback for the portable summary.

Daily feature flags

These go with install.active. The app sends a flag only when the install used that feature that day.

FlagFeature
worker_sessionWorker sessions in a Hive
waggleWaggle
worktreeManaged worktrees
terminalThe built-in terminal
browser_previewThe browser preview
browser_agent_drivenAn agent driving the browser preview
project_actionProject actions
inline_visualizationInline visualizations
attachmentAttachments on messages
voiceVoice input
fork_or_handoffForking a conversation or handing off a session

Catalog values

Provider, model, MCP server and skill values outside the public catalogs become custom, in the app and again at the endpoint.

ValueCatalog
provider, modelPi’s built-in providers and their models
mcp_serversOpenWaggle’s curated MCP catalog, by catalog name, such as playwright or chrome-devtools
skillsSkills built into OpenWaggle. Today that is only visualize

An MCP server counts as a catalog server only when its name matches a catalog name, with - and _ treated alike, and it runs exactly as the catalog installs it: the same command and arguments, or the same URL. Any other server is custom, including a server of your own that only shares a catalog name.

Limits

LimitValue
app.opened20 events per day
update.installed5 events per day
Run events150 per day, run.finished and run.compacted together
Install events1 per day each of install.active, install.new and install.onboarding
List entries32 in mcp_servers, and 32 in skills
ID length128 characters, for a provider, model, server or skill ID
ID charactersLetters, digits, ., _, :, /, @ and -, starting with a letter or digit
Request events200 in one request
Request size256 KiB
Oldest day35 days back, for what the app sends and what the endpoint accepts
Newest day1 day ahead of the endpoint’s own UTC day

The app drops events past a daily limit and never sends them later. Each request covers one UTC day. A list such as mcp_servers may not repeat a value.

Never sent

What OpenWaggle collects and why lists what usage statistics never contain.

Error reports

An error report covers one of these:

  • an error the app reports on purpose
  • an error that nothing else handled, which the report tags as unhandled
  • an Electron helper or renderer process that ended abnormally, reported only by its process type and exit reason

A report keeps only these fields:

FieldContents
Error typeThe error’s class name. A type defined by code outside the app, such as a Pi extension, becomes Error
CodeA short code, such as an HTTP status (http-429) or a Node.js code (ECONNRESET)
Stack traceScrubbed as described below
Time and processWhen it happened and which OpenWaggle process reported it
AppApp version and build channel
MethodFor an unhandled rejection from one of the app’s own API calls, the method’s name, such as getSettings, taken from OpenWaggle’s own bridge
SystemOperating system name and version, CPU architecture, and the Electron, Chrome and Node.js versions

The app drops the message text of every report, because a message can quote your files, commands or model output. The one exception is a handled error that the app reports as an application error, which it does only where the message cannot hold your content. Today that is one report: when the app or its Session Host fails to start, or the Session Host stops on an error, the app reports a summary built only from fixed values. It names the process, the type of each error in the chain, any Node.js error code, and, for a built-in Windows helper, the step it reached, its exit code and signal, and a Windows error code, for example session-host: Error <- WindowsUserOnlySecurityError stage=compile exit=1. Any other error type becomes Error, unless it is built in or one of the app’s named startup errors. The summary never includes an error message, path or helper output.

What the app replaces

Before a report leaves your machine, the app replaces:

PlaceholderWhat it replaces
~Your home directory, in each form listed below
<tmp>macOS per-user temporary folders under /var/folders, and your temporary directory, such as Windows %TEMP%
<scratch>OpenWaggle scratch and evidence folders
<id>UUIDs, such as session and run IDs
<hex>Other hexadecimal runs of 16 or more characters
<external>Stack frames from code outside the app, such as a Pi extension, a worktree or any other folder

The app recognizes your home directory as /Users/<name>, /home/<name>, /var/home/<name>, /root, /System/Volumes/Data/Users/<name>, C:\Users\<name> with either separator, \Users\<name> without a drive, \\wsl.localhost\<distro>\home\<name>, \\wsl$\<distro>\home\<name>, \\wsl.localhost\<distro>\root, and /mnt/<drive>/Users/<name>. A Windows name ends only at a separator, a character Windows forbids in names, or the end of a line, so the app replaces names with spaces or apostrophes whole.

An external frame keeps its file name only when the file is named index, as in <external>/index.js. The app drops its function and module names, and reduces debug information for that code the same way. Shared folders stay as they are: /Users/Shared, and Public, Default, Default User and All Users under C:\Users.

The app also removes user details, request data, the server name, breadcrumbs, the list of loaded modules, local variables and source lines. The locale, time zone, memory figures, boot and start times, and device name never leave. The app sends no screenshots or session replays, and native crash dumps stay on your machine.

Sentry’s session tracking is off, and only error events leave the app. Before Sentry receives a report, the endpoint removes your IP address and applies the same scrubbing again. It forwards only error events, so session data, attachments, crash dumps and replays never reach Sentry. It drops any report it cannot scrub.

Provider request headers

Pi labels requests to a few model providers with extra headers. The labels go to that provider with your request, never to OpenWaggle. The statistics switch decides them.

ProviderStatistics onStatistics off
OpenRouterHTTP-Referer: https://openwaggle.ai and X-OpenRouter-Title: OpenWaggleNone
NVIDIA NIMX-BILLING-INVOKE-ORIGIN: OpenWaggleNone
opencodex-opencode-client: OpenWaggleNone

The OpenRouter labels let OpenRouter’s public app rankings credit OpenWaggle. OpenWaggle removes the X-OpenRouter-Categories header that Pi would otherwise add. It leaves headers you configured yourself alone, and it never writes its switch into Pi’s ~/.pi/agent/settings.json. Setting PI_TELEMETRY to anything other than 1, true or yes turns statistics off, and Pi then adds none of these labels.

Session titles, MCP sampling requests made for an MCP server, native compaction requests, and model calls from codemode scripts carry no labels. Conversation summaries made for compaction, and branch summaries, carry the same labels as the conversation’s own requests.

These headers do not depend on the switch:

RequestsHeader
Most providersUser-Agent naming Pi, with the Pi version, operating system, runtime and processor architecture, such as pi/1.6.0 (darwin; node/v24.0.0; arm64)
Amazon Bedrockpi/1.6.0 added to the AWS SDK’s own User-Agent
GitHub CopilotCopilot’s own User-Agent
Claude subscriptionAnthropic’s command-line client User-Agent, claude-cli
ChatGPT subscriptionPi’s User-Agent and originator: pi
opencodex-opencode-session with the Pi session ID, which opencode uses to tell sessions apart

Endpoint routes

The app sends statistics to https://openwaggle.ai/api/v1/events and error reports to https://openwaggle.ai/api/v1/errors. The endpoint is a Cloudflare Pages Function, deployed with the website.

The endpoint accepts only requests shaped like the app’s own. It requires the expected JSON or Sentry envelope content type, and it forwards only to PostHog’s and Sentry’s EU hosts.

Request Origin/web/errors/events and the job routes
None, as the app sends statisticsRefusedAcceptedAccepted
nullRefusedAccepted, because Electron’s network layer can send itRefused
https://openwaggle.aiAcceptedRefusedRefused
Any other http or https addressRefusedRefusedRefused

/web accepts only beacons from openwaggle.ai pages. During development it also accepts a loopback page when the endpoint runs on loopback.

Web pages cannot send app requests anyway. The required content type makes the browser ask the endpoint first, in a CORS preflight, and the endpoint refuses it.

Storage and publishing

The endpoint never forwards a statistics request as it arrived. It stores each accepted request in Cloudflare KV as one entry of counts, under a random key that ties it to no install and no arrival time. An entry holds one install’s report for one UTC day. It stays until the daily job publishes it, and at most 45 days after its day ends. The expiry comes from the day, not from when the entry arrived.

Once a day, OpenWaggle’s GitHub workflow runs an authenticated job that adds up each day’s entries.

StepWhat happens
TotalsCounts for each event, field and value. A number field such as duration_s becomes a sum and a count
Publish timeA day goes out once at least 5 reports of that day can be added up, and in any case once the day is 7 full UTC days old
ThresholdA value, list item or number sum appears only when at least 5 distinct reports contributed to it
Small valuesMerged into (other). If (other) would stand for fewer than 5 reports, the next smallest values fold in too. If nothing is left, the job drops the breakdown
Missing valuesReports without a value, such as installs that did not use a feature, count as their own group for the threshold
Small sumsLeft out
Event totalsAlways published, so a week-old day with fewer than 5 reports publishes only how many times each event happened

Before it sends a batch, the job records the exact set of entries in a flush manifest. Each published row carries a UUID derived from that set of reports and from what the row counts, so a retried flush resends identical rows and PostHog drops the repeats. Once PostHog accepts the batch, the job deletes the entries. If a delete fails, it writes a small flushed: marker for that entry instead, so the entry is never published twice, and it keeps the manifest until every entry is deleted or marked. The markers and the manifest hold no counts and expire with their entries.

Each record in PostHog is a total for one field and value. Every total arrives under one fixed ID that all installs share, filed at noon UTC on its day, with person profiles and PostHog’s own location lookup turned off.

Endpoint logs

The endpoint writes one log line for each request it handles, with only these fields:

FieldValues
pathThe route, or (unknown) for a path it does not serve
outcomeaccepted, rejected, forward_failed, skipped or error
fieldThe name of a rejected field
accepted, rejectedHow many events it accepted and rejected
statusThe HTTP status code
latency_msHow long the request took

It never logs your IP address, request headers, or the values you sent. The endpoint counts requests to /events only inside the daily totals, as endpoint.requests. Requests to the other routes also send an endpoint.request event with the same fields to PostHog. A request to a path it does not serve is only logged. Cloudflare’s stored request logs stay off for the endpoint, because they can include the client IP address. Exceptions inside the endpoint go to Sentry.

Website statistics

The openwaggle.ai website reports to the same endpoint, at /api/v1/web, and to the same PostHog project. For each visit it records:

ItemRecorded as
Page viewsThe path and time, without query strings or fragments
ReferrerThe referring page’s origin and host name, such as https://example.com, never its path
Channelsearch, social, referral or direct
CampaignUTM tags in the link you followed
CountryTwo-letter country code
Download clicksThe kind of link, never the link itself: github_releases, release_asset, install_script or installation_page

To count visitors, and to connect a landing page with a download click later that day, the endpoint derives a visitor key from your IP address, your browser’s User-Agent, and a random salt for the current UTC day. PostHog receives the key, never the address or User-Agent. The salt expires at the next UTC midnight, or up to a minute later when the endpoint creates it in the last minute of a day, because Cloudflare KV keeps a value for at least a minute. The endpoint never uses a salt after its day ends. App reports never use a visitor key.

If Cloudflare KV is unavailable, the endpoint uses a salt kept only in the memory of that server instance for that day, and never writes it anywhere. Visitors served by different instances then get different keys, so the visitor count may run a little high.

The site’s Content Security Policy allows only the statistics endpoint. The endpoint drops any beacon that carries DNT: 1 or Sec-GPC: 1.