CherryHQ/cherry-studio

[Discussion]: How to fully disable analytics

Closed

#15,267 opened on May 22, 2026

View on GitHubContributor guide
 (1 comment) (1 reaction) (0 assignees)TypeScript (4,338 forks)batch import
discussionhelp wanted

Repository metrics

Stars
 (45,688 stars)
PR merge metrics
 (Avg merge 3d 6h) (306 merged PRs in 30d)

Description

Issue Checklist

  • I understand that issues are meant for feedback and problem-solving, not for venting, and I will provide as much detail as possible to help resolve the issue.
  • I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
  • I confirm that I am here to ask questions and discuss issues, not to report bugs or request features.

Platform

macOS

Version

1.9.6

Your Question

How to fully disable analytics?

Context

No response

Additional Information

Priority

Medium (Would like a response soon)

Contributor guide

Research direction
The issue asks how to fully disable analytics. First, check the application's settings UI for an analytics toggle. If not present, look for a configuration file (e.g., .env) or documentation. If no option exists, this may require a feature request to add a disable analytics flag. Consider reviewing the codebase for analytics initialization (likely in a main.ts or analytics module) to understand current implementation.
Tech stack
typescript
Domain
frontend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90