cherry-studio

CherryHQ/cherry-studio

Your AI workspace for models, agents, and productivity.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
12 Nov 2026
today
Ship score
99/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 52,220 → 53,387 (29 Sep – 10 Nov 2026)
+804 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
53.4K
Forks
5.2K
Open issues
2.6K
Watchers
204
Primary language
TypeScript
Created
24 May 2024
Owner
CherryHQ · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 212 startups in the directory ship primarily in TypeScript.

Topics

#agent-skills#agent-workspace#agentic-workspace#ai-agents#ai-models#ai-productivity#ai-workspace#computer-use#llm#mcp-client#ollama

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 100%, self-hostable 19%, hosted offering 48%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 12 Nov 2026This is the badge for CherryHQ/cherry-studio, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/CherryHQ/cherry-studio.svg)](https://ossean.com/CherryHQ/cherry-studio)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.