Disable Analytics

[soyllamas]

Use case

The CLI currently fails to execute commands when analytics tracking calls are blocked by custom DNS configurations (e.g., DNS-level ad/tracking blockers). This makes the CLI unusable for users who implement network-level privacy controls.

Proposal

1. Add a user-configurable analytics flag:
   • Allow users to disable analytics via CLI flags (e.g., patrol --disable-analytics or patrol --analytics=false).
   • This gives users explicit control over analytics collection.
2. Implement "fire and forget" analytics:
   • Make analytics non-blocking by running it asynchronously.
   • Analytics failures won't affect command execution or user experience.
   • Main command continues regardless of analytics success/failure.

[pdenert]

Hi @soyllamas. Thanks for the issue.
Currently, at the first run, patrol asks whether you agree for analytics or not. If you don't agree, patrol won't be sending analytics.
If you agreed for analytics, but now want to disable it, you can find file $Home/.config/patrol_cli/analytics.json and change: "enabled":true to "enabled":false. Alternatively, you can delete this file and the next time you launch patrol it will ask for analytics permission again.