How to use
Cherry Studio.

1. 01

   Start at https://www.cherry-ai.com/ and confirm the domain before entering account or payment information.

2. 02

   Availability: Cherry Studio provides signed desktop releases for current Windows, macOS, and Linux systems, plus related mobile development; official release assets include platform-specific installers and hashes.

3. 03

   A supported operating system, an official verified installer, provider API keys or local endpoints, enough storage for conversations and knowledge bases, a backup location, and explicit permissions for files, search, agents, skills, and MCP tools.

4. 04

   Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

5. 05

   Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

• Use official download pages.
• Review permissions during setup.
• Keep installers and applications updated.

1. 01

   Download a current official release, verify the asset and hash where supplied, back up existing data before upgrades, and review operating-system and license requirements.

2. 02

   Add one provider with a dedicated low-privilege key or a local endpoint, keep the official base URL, fetch and allowlist only required models, and enable the provider after a connectivity test.

3. 03

   Create a narrowly instructed assistant and run a non-sensitive benchmark for output quality, provider routing, context, file handling, search, latency, errors, and token cost.

4. 04

   Review the selected provider's privacy terms and data path, configure encrypted backups, then add knowledge, skills, agents, or MCP only after separate permission and supply-chain review.

• State the outcome before the background.
• Provide the real source material.
• Review the result before expanding the task.

1. 01

   Restate the original outcome and acceptance criteria before reviewing the response.

2. 02

   Mark every factual claim, calculation, quotation, or figure that could materially affect the result.

3. 03

   Check those items against the original source, a primary reference, or direct inspection.

4. 04

   Ask the tool to list its assumptions and uncertainty, but never rely on self-review as the only check.

5. 05

   Complete a human edit for relevance, tone, privacy, accessibility, and the exact delivery format.

• Verify consequential claims independently.
• Fluency is not accuracy; confident phrasing is not evidence.
• Keep a record of sources and review decisions.

1. 01

   Classify the task and its data before uploading or connecting anything.

2. 02

   Review the product, account, organisation, retention, and training settings that apply to you.

3. 03

   Grant the narrowest file, workspace, microphone, screen, or integration permissions needed.

4. 04

   Remove secrets and personal or regulated information unless your approved policy explicitly permits it.

5. 05

   Review the output and revoke permissions or disconnect sources that are no longer needed.

• Cherry Studio stores local workspace data and keys but sends prompts and selected content to configured providers and may call search, embedding, backup, MCP, agent, or mini-app services. Local storage is not automatic encryption or backup. Use official builds, dedicated keys, approved endpoints, device encryption, narrow filesystem roots, reviewed MCP packages and skills, human approval for actions, and tested encrypted backups before upgrades.
• Follow your organisation's approved-use policy.
• Never treat fluent output as authorization to act.

• Cherry Studio project overview ↗
• Official Cherry Studio releases ↗
• Model provider settings ↗
• Cherry Studio privacy policy ↗

Working on something like this? See how we handle product design, or book a call.