CLI telemetry

What is collected

When the service enables analytics, Juiced reports completed installs, first runs, successful Juiced logins, session connections, and basic session activity to PostHog. Events include CLI version, OS, architecture, and a random installation ID. After login, an opaque user ID connects usage across your computers.

Analytics never includes prompts, source code, terminal output, command arguments, file paths, repository names, email addresses, or credentials. PostHog GeoIP enrichment is disabled. Hosting and authentication logs are separate.

Control collection

$ juiced telemetry status
$ juiced telemetry disable
# To enable again:
$ juiced telemetry enable

The preference is stored on this computer and survives upgrades. Set JUICED_TELEMETRY_DISABLED=1 or DO_NOT_TRACK=1 to override it. CI and self-managed mode disable product telemetry.

$ curl -fsSL https://juiced.codes/install.sh | JUICED_TELEMETRY_DISABLED=1 sh

For future CLI runs, also set the environment variable in your shell or run juiced telemetry disable after installing. Telemetry settings work offline. Reporting failures never fail an installation or command.

How activity is measured

A session connection is counted after the agent or terminal is ready. Activity is recorded when input is accepted or an attached interactive agent is working, at most once per five minutes per CLI process. Idle sessions do not emit activity. Logout resets the anonymous identity used for account linking; the installation ID survives. Deleting local configuration creates a new ID.