Telemetry Control
Both
DISABLE_TELEMETRY and DO_NOT_TRACK have the same effect. Use whichever you prefer.Skill Discovery
GitHub Authentication
CI Detection
The CLI automatically detects CI environments and adjusts behavior (e.g., disables telemetry). These variables are read-only (set by CI platforms, not by users).CI
CI
Generic CI environment indicatorSet by: Most CI platforms
Example:
Example:
CI=trueGITHUB_ACTIONS
GITHUB_ACTIONS
GitHub Actions environmentSet by: GitHub Actions
Example:
Example:
GITHUB_ACTIONS=trueGITLAB_CI
GITLAB_CI
GitLab CI environmentSet by: GitLab CI/CD
Example:
Example:
GITLAB_CI=trueCIRCLECI
CIRCLECI
CircleCI environmentSet by: CircleCI
Example:
Example:
CIRCLECI=trueTRAVIS
TRAVIS
Travis CI environmentSet by: Travis CI
Example:
Example:
TRAVIS=trueBUILDKITE
BUILDKITE
Buildkite environmentSet by: Buildkite
Example:
Example:
BUILDKITE=trueJENKINS_URL
JENKINS_URL
Jenkins environmentSet by: Jenkins
Example:
Example:
JENKINS_URL=https://jenkins.example.comTEAMCITY_VERSION
TEAMCITY_VERSION
TeamCity environmentSet by: TeamCity
Example:
Example:
TEAMCITY_VERSION=2023.11When any CI variable is detected, the CLI automatically:
- Disables telemetry (unless explicitly re-enabled)
- Adds
ci=1flag to any telemetry that is sent - May adjust interactive prompts (some CI platforms)
Examples
Development Workflow
CI/CD Pipelines
Shell Configuration
Complete Reference
table
Related Documentation
Telemetry
Learn more about what telemetry data is collected
Lock Files
See how GitHub tokens are used to fetch skill hashes