#Global flags

Use global flags to control CLI behavior consistently across commands, especially for telemetry and machine-readable output.

Extension.js telemetry is intentionally anonymous and privacy-safe. It should remain less invasive than hosted-product analytics patterns commonly seen around web framework tooling.

#Global flag capabilities

#Global options

#Practical examples

#Disable telemetry for a CI build

extension build --browser=chrome,firefox --no-telemetry

Use this when policy requires explicitly disabling telemetry for specific automation runs.

#Generate machine-readable help for tooling

extension dev --ai-help --format=json

Use this for AI tooling, wrappers, or scripts that parse command help output.

#Keep readable help output for local debugging

extension dev --ai-help --format=pretty

Use pretty mode when you want assistant-friendly output that still reads well in terminal sessions.

#Notes

• Global flags are parsed before command-specific options.
• Telemetry behavior and privacy details are documented in repository TELEMETRY.md and in Telemetry and privacy.
• Command pages document command-specific flags separately.
• Global flags can be combined with command-specific options.
• For machine consumers (AI/CI), command readiness should come from dist/extension-js/<browser>/ready.json, not terminal log parsing.

#Next steps

• Apply these flags in create and dev workflows.
• Use them for production checks in start, preview, and build.