Cherry Studio Guide: Your AI Workstation | Part 1
One desktop workspace for conversations, documents and AI tools. Start this four-part Cherry Studio with Omnirouter series with a practical first workflow.
By omnirouter
Practical AI with Cherry Studio and Omnirouter — Part 1 of 4.
Cherry Studio brings model conversations, reusable assistants and other AI tools into one desktop workspace. Omnirouter supplies prepaid model access through a compatible API. Put them together and you can organize your work in one client while choosing a model for each job, instead of making one expensive model your default for everything.
This guide starts with what the workstation does and a small workflow you can repeat. The next parts connect the API, add documents and tools, and measure spending.
What Cherry Studio can do
The official Cherry Studio introduction describes multi-model conversations, assistants, knowledge bases, translation, AI drawing and agent capabilities. The official project provides desktop builds for Windows, macOS and Linux.
| Capability | A useful first task | What you still need |
|---|---|---|
| Multi-model conversations | Compare two explanations of a bug | Access to both models; each answer can incur usage |
| Reusable assistants | Keep your documentation style instructions together | Clear instructions and a suitable model |
| Documents and knowledge | Ask questions grounded in your own material | Supported files and the required retrieval setup |
| Translation and writing | Rewrite a release note for a different audience | Human checks for meaning and technical terms |
| AI drawing | Produce concepts for a cover or diagram | A configured, compatible image provider |
| Agent work | Turn a bounded request into a sequence of actions | A supporting app version, tools and explicit permissions |
These are client capabilities, not a promise that every model or API provider supports every feature. A successful text conversation does not establish image generation, embeddings, vision or tool compatibility.
Your first useful workflow: turn notes into a release brief
Start with public or synthetic material, not production secrets. Install Cherry Studio from its official distribution, configure a provider, and select a text model. If you want prepaid access through Omnirouter, follow Part 2: connect your account.
Create an assistant for release notes. Give it a narrow instruction: preserve the supplied facts, separate shipped work from plans, and never invent a date or feature. Start a new conversation and paste a short set of sample notes.
Try this prompt:
Turn these notes into a release brief. Use three sections: shipped, known limitations, and next steps. Keep the result under 180 words. Use only the supplied facts. Mark missing information as unknown. Do not invent customer quotes or performance numbers.
Check whether every claim traces back to your notes. Save the useful result with its source material. The repeatable asset is the instruction and review process, not a single impressive response.
Compare models without turning comparison into busywork
Cherry Studio supports asking multiple models the same question. Use that selectively. Compare two models on the same notes and grade factual accuracy, completeness and editing time. A longer answer is not automatically better, and agreement between two models is not proof.
Once a lower-cost model meets your standard, use it for routine drafts. Keep a second model for cases that fail your checks. Comparison calls consume additional tokens; they are an evaluation expense, not a free quality switch.
What Omnirouter adds
Omnirouter provides a model catalog and prepaid balance rather than a monthly subscription. You configure the endpoint and your key in the client, then select an available model. See the current catalog and billing explanation before adding credit.
For routine work, start by evaluating available GLM, DeepSeek, Qwen, Kimi or MiniMax options. These families are the intended backbone of our budget offering. That is an operational preference, not an uptime guarantee or a claim that every variant has open weights. Cheap frontier access can be more volatile as upstream capacity changes; keep a tested alternative.
A desktop client is not the same as offline AI
A local application can still send prompts, document excerpts and images to remote providers. Review the data handling of each service you enable. Keep API keys out of messages, screenshots and exports. Local-model options and remote APIs have different privacy and hardware trade-offs.
Before enabling agents, first get one ordinary text conversation working. Add capabilities individually so you know which component is responsible when something fails.
Continue the series
- You are here: Cherry Studio as your AI workstation.
- Connect Cherry Studio to Omnirouter.
- Build document and tool workflows.
- Choose models and control token costs.
Scope: This is an independent Omnirouter tutorial, not an official Cherry Studio partnership. Menu labels and capabilities can differ by version. Cover artwork is illustrative, not an application screenshot; the Cherry Studio icon identifies the project.