Compatible (BYOK)

Use Cherry Studio with GlideflowAI.

A desktop AI client with custom OpenAI-compatible provider support. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.

Get a key

What this connection is for

Cherry Studio is a desktop AI client for conversations, document-oriented work, and switching among user-configured model services. It fits people who want a local application to organize chats and provider profiles without tying the interface to one model account. The provider layer can be changed independently of the conversation workspace, which is useful for deliberate BYOK experimentation.

Choose Cherry Studio when a desktop chat client is more useful than a coding agent or a hosted workflow builder. It is less appropriate when your main need is automated repository editing, scheduled jobs, or server-side application orchestration. Because provider forms vary across releases, test a new connection with a disposable chat before importing a large history or shared preset.

Cherry Studio documents custom OpenAI-compatible providers. Use GlideflowAI's endpoint, key, and an exact catalog model in the current provider form, while confirming whether that release expects a full /v1 URL or appends request-path segments itself. Record the tested version with the profile if several machines share the same chat workflow. Cherry Studio is an independent project; this is a user-managed connection, not an endorsement or partnership.

Why pair it with GlideflowAI

Cherry Studio lets you keep locally organized conversations while GlideflowAI supplies a separately managed compatible model route.

The public catalog helps when you want to add a model by ID instead of relying on a desktop client's built-in provider list.

Setup

Use a new API key for the tool, select a model from the catalog, and begin with a small task. Do not put a key in a repository, screenshot, or shared configuration file.

1
Add a custom compatible provider
Use Cherry Studio's supported provider-management surface to add an OpenAI-compatible provider. Provider labels can vary between releases.
```
Provider type : OpenAI Compatible
```
2
Enter the connection values
Use the GlideflowAI URL, a private API key, and an exact model ID. Make a short chat request before importing shared settings.
```
Base URL : https://api.glideflowai.com/v1
API key  : sk-your-key
Model ID : kimi-k3
```

Before you begin: Manual check: confirm whether the installed Cherry Studio release expects the full /v1 URL or appends part of the request path itself.

Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing.

Frequently asked questions

Should Cherry Studio receive the full /v1 URL?

Check the installed release's provider documentation first: Cherry Studio versions can append request paths differently, so verify before saving the profile.

Can I store several GlideflowAI keys in Cherry Studio?

Use the client’s supported provider or key-management mechanism and keep each key local; do not export a profile containing secrets.

What should I test after saving a provider?

Start a new short chat with one exact model ID, then confirm responses arrive before reusing the profile in a knowledge-base workflow.

Is this an official integration?

No. The connection is configured by you using a compatible API and does not imply sponsorship, endorsement, or a partnership.

Ready to connect Cherry Studio?

Create a key, use the setup above, and verify the connection on a small task before you scale it up.