RadarTopicsBuildersWeeklyReads
Open Source Radar
CherryHQ/

cherry-studio

GitHubWebsite

Cherry Studio is a desktop client that supports multiple LLM providers, offering 300+ AI assistants, cross-provider workflows, and document processing features. It emphasizes multi-model conversations, integration with various services, and a cross-platform desktop experience.

49kstars
4.7kforks
1.2kissues
AGPL-3.0license
2024since
Star historydaily snapshots by VibeCrowd

Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).

Alternatives & relatedmatched by topic overlap
Reviewgenerated from repository data · Aug 5, 2026

What it is

Cherry Studio is a desktop client that supports multiple LLM providers, available on Windows, Mac and Linux. The project presents itself as an AI productivity studio with smart chat, autonomous agents, and 300+ assistants, aiming to provide unified access to frontier LLMs.

How it works

The repository highlights support for diverse LLM providers (OpenAI, Gemini, Anthropic, and more), integration with AI web services (Claude, Perplexity, Poe, etc.), and local model support via Ollama and LM Studio. It also features AI assistants and conversations, document and data processing capabilities, and various tools integrations (global search, translation, markdown rendering, etc.). The project includes a Model Context Protocol server (MCP) and supports cross-model, multi-conversation workflows. The README enumerates capabilities across several areas, including data formats (text, images, PDF, office), WebDAV for file management, Mermaid chart visualization, and code syntax highlighting.

Getting started

From the README, the Getting Started section outlines typical open-source contribution steps: fork, create a branch, submit changes, and open a PR, with a reference to a Contributing Guide. Specific commands for setup or local development are not provided in the excerpt.

Recent releases

Latest releases shown:

  • v2.0.0 (2026-08-05): Cherry Studio 2.0.0 - A New AI Workspace, from Chat to Getting Work Done
  • v2.0.0-rc.5 (2026-08-04): Fixes and updates including provider-registry change and daily I18N sync
  • v1.9.13 (2026-08-03): Various fixes and feature updates related to models and thinking capabilities
  • v2.0.0-rc.3 (2026-07-31): Appearance and resource group updates
  • v2.0.0-rc.2 (2026-07-29): Data/model migration fixes

Quotes and exact changelog entries are included in the Releases section of the README.

Traction

The repository shows 49,400 stars, 4,694 forks, and 1,205 open issues. It is primarily written in TypeScript and licensed under AGPL-3.0. These numbers are provided in the repository metadata and are not elaborated beyond the counts here.

Behind the repo

No explicit startup or company linkage is detailed in the excerpt beyond project-wide enterprise edition notes describing centralized model management, knowledge bases, and private deployment capabilities for teams.

Caveats

License: AGPL-3.0. Age: Created 2024-05-24. Open issues count is 1205. These data points are stated in the repository metadata. No further licensing or issue-level caveats are described in the provided material.

Agent skills inside · 19
All skills →
skill-creatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Testing & QAscriptsvercel-react-best-practicesReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.Data & Analyticsgh-pr-reviewAutomated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.Frontendcherry-tool-guideCherry Studio first-party tool routing guide for general agents. Use this WHENEVER a task could be served by Cherry's built-in tools — even if the user never names a tool — including researching current/online information or requesting browser interaction (Cherry's web built-ins search and fetch but do not automate pages), answering from the user's own documents and knowledge bases, recalling or saving things across sessions (persistent memory), scheduling recurring or one-time tasks and sending notifications, connecting or repairing IM channels (Telegram/Feishu/Discord/Slack/WeChat/QQ), generWorkflow & Productivityclaude-automation-recommenderAnalyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.AI & Agentscherry-electron-devDevelop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.Frontend
SharePost on XLinkedIn
All trending reposRevenue-verified startups →