For the complete documentation index, see llms.txt. This page is also available as Markdown.

Online Mode

How to use Online Mode in Cherry Studio

The online mode lets the AI search for the latest content before answering, which is suitable for the following scenarios:

  • Time-sensitive information: news, prices, exchange rates, etc. from today / this week / just now

  • Real-time data: dynamic values such as weather, stock prices, and product inventory

  • Emerging knowledge: newly emerged tools, concepts, and technologies

How to enable online mode

Click 🌐 in the toolbar of the chat input box globe icon to enable online mode for the current conversation.

The globe icon in the chat input bar: click it to enable online mode for the current conversation (the prompt will show the current search service provider)

Ready to use out of the box: Cherry Studio already has built-in Exa MCP as the search service provider,no API key configuration is required(using the public MCP endpoint mcp.exa.ai), and the default URL fetching provider is Jina. So after installation, you can click 🌐 to search online directly.

Whether it uses the configured service or the model's built-in

path for online access is determined by the “Prefer configured search service” toggle; it is enabled by default:

  • On (default): clicking 🌐 will use the service you configured in Settings → Web Search — initially, this is the key-free Exa MCP.

  • Disable: if the model itself natively includes search(there is a small globe icon 🌐 next to the model name), then the model handles online access itself.

For native online support, refer to the 🌐 icon next to the model name; do not rely on a fixed model list. Common current cases include:

  • DeepSeek: models that support this capability can use native web search;

  • OpenRouter: chat models can use native web search and URL content retrieval;

  • Alibaba Cloud Bailian: models that support this capability can use native web search, and some Qwen models also support URL content retrieval;

  • Some models from providers such as Google Gemini, Zhipu AI, and xAI Grok also support native online access.

Model capabilities vary by provider. When choosing a model, look for the 🌐 icon; if there is no icon, using the configured search service is safer.

A few models can still go online even without showing the small globe icon (depending on provider configuration). For example Volcengine online access integration describes one such case.

Configure services in Settings

After opening Settings → Web Search, configuration is split into two parts, and each part uses a dropdown to choose the service provider,the selected one will serve as the default for that capability:

section
Effect

Search provider

Search web pages based on your question and return summary results

URL fetch provider

Fetch the main text of a webpage from a specified URL to supplement the search results

Web search settings: the two sections, Search provider / URL fetch provider, and the bottom “Prefer configured search service” toggle

Built-in providers

The following services are built in, divided into API and MCP two types:

service
Type
Capability
Explanation

Exa MCP

MCP

Search

By default, ready to use without an API key

Tavily

API

Search

A search engine optimized for LLMs

Bocha

API

Search

A Chinese search API for AI scenarios, with real-time web pages + structured results

Exa

API

Search

Neural search designed for AI applications, good at semantic retrieval

Zhipu

API

Search

Zhipu GLM Web Search, online search and real-time information

Querit

API

Search

A web retrieval service for AI applications

SearXNG

API

Search

A free, self-hostable metasearch engine

Firecrawl

API

Search

Web crawling and search, can convert results to Markdown

Jina

API

Search · URL fetch

Jina Reader; also the default URL fetch provider

Fetch

API

URL fetch

Built-in URL fetching, retrieves the main text from a specified URL

Besides the default Exa MCP(key-free), most API providers require their own API keys;SearXNG enter a self-hosted address,Fetch is built in and requires no configuration.

Advanced settings

  • Number of search results: how many items to return per request (default 5, maximum 100). If compression is not enabled, a larger number will consume more tokens.

  • Search result compression: compress the returned content before feeding it to the model to save tokens. The default is “truncation,” with a default truncation length of 2000 characters; you can also switch to “no compression” or adjust the truncation length.

  • Search result blocklist: block websites you don't want to appear; see Web search blocklist configuration.

Advanced settings: number of search results, compression method (no compression / truncation), blocklist

The default Exa MCP can be used without an API key; if you want to switch to other services or dive into advanced configuration, see the articles below:

How it works

No matter which method is used, the conversation flow is:

  1. You ask, “How's the weather in Shanghai today?”

  2. Cherry Studio first sends the question to the search service

  3. The search service returns relevant webpage summaries

  4. Cherry Studio adds these summaries to the prompt and sends them to the AI model

  5. The AI answers you based on real-time data


Get help and submit feedback

If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to Feedback and Suggestions for the official channels provided.

Last updated

Was this helpful?