Skip to content

armgit / cindy

Public Imported from GitHub
0

Consider it done. The open-source AI agent that works out of the box · 想到,就能做到。开源、开箱即用的 AI Agent。

docs(help): 说明网页搜索默认走 Cindy AI、无需配置 key

Dash0a76fd2fcfe4
diff --git a/apps/desktop/help-knowledge/connections.md b/apps/desktop/help-knowledge/connections.md
index 8d375be4de..f64b4b52ce 100644
--- a/apps/desktop/help-knowledge/connections.md
+++ b/apps/desktop/help-knowledge/connections.md
@@ -14,7 +14,7 @@ External account connections have moved out of the old "Third-Party Platforms" s
- **GitLab** — handled by the Cindy GitLab plugin (Plugins > Cindy GitLab; existing PAT connections are migrated automatically).
- **Codex** — sign in under Settings > Model Providers (separate from the Codex CLI binary the app ships with).
- **FeiShu** — bot only (App ID / Secret under Settings > IM bots; see the FeiShu bot topic). FeiShu is no longer a sign-in method for Cindy itself.
-- **Cindy AI** — Settings > Model Providers. Web-search keys are configured on the matching plugin detail page (Cindy Web Search).
+- **Cindy AI** — Settings > Model Providers. Cindy Web Search uses this account by default and needs no key; optional Brave / Tavily / DeepSeek search keys are configured on that plugin's detail page.
**Managing connections:**
diff --git a/apps/desktop/help-knowledge/plugins.md b/apps/desktop/help-knowledge/plugins.md
index e37359d609..7157b9a3e4 100644
--- a/apps/desktop/help-knowledge/plugins.md
+++ b/apps/desktop/help-knowledge/plugins.md
@@ -15,7 +15,7 @@ Plugins (internally "意识" / Ghost) extend what the agents can do — they add
**Built-in plugins that ship with the app:**
- **Cindy Art** (`$cindy-art`) — generate and edit images and short videos.
-- **Cindy Web Search** (`$cindy-web-search`) — public web search (add your own Brave or Tavily key on its detail page).
+- **Cindy Web Search** (`$cindy-web-search`) — public web search. **No key needed**: by default it searches through Cindy AI and uses your signed-in Cindy account's balance (unavailable in local mode). Results come with a title, link, and short summary. To search through your own service instead, add a Brave, Tavily, or DeepSeek key on its detail page. A failed search is reported as-is; it never silently switches to another source.
- **Cindy Mermaid** (`$cindy-mermaid`) — build / repair Mermaid diagrams.
- **Cindy GitHub** (`$cindy-github`) / **Cindy GitLab** (`$cindy-gitlab`) — read / write issues, PRs / MRs, reviews, CI, releases.
- **Filo Google** (`$filo-google`) — Gmail / Calendar / Drive / Sheets.
@@ -54,7 +54,7 @@ Plugins (internally "意识" / Ghost) extend what the agents can do — they add
**Configuring a plugin's account / API key:**
-- Do it on the plugin's **detail page**. Plugins that use a key (web-search, GitHub/GitLab tokens) have a field there; the value goes straight into the host's encrypted store and can't be read back.
+- Do it on the plugin's **detail page**. Plugins that use a key (optional search-service keys for Web Search, GitHub/GitLab tokens) have a field there; the value goes straight into the host's encrypted store and can't be read back.
- Plugins that use OAuth (for example Filo Google) show a **Connect account** button instead.
**Notes:**
diff --git a/apps/desktop/help-knowledge/providers.md b/apps/desktop/help-knowledge/providers.md
index e1d72c3a8c..3b868f7677 100644
--- a/apps/desktop/help-knowledge/providers.md
+++ b/apps/desktop/help-knowledge/providers.md
@@ -23,5 +23,5 @@ Claude Code, Codex, and lightweight utility models can use **Cindy AI** for pay-
**Notes:**
-- Direct service keys such as Brave Search and Tavily are **not** managed here — they live on the matching plugin detail pages under Plugins (Cindy Web Search).
+- Direct service keys such as Brave Search, Tavily, and DeepSeek search are **not** managed here — they live on the matching plugin detail pages under Plugins (Cindy Web Search). They are optional; web search works through Cindy AI without them.
- Rotating or replacing credentials takes effect for new turns; in-flight requests finish on the previous key.
diff --git a/apps/desktop/src/main/maker-ipc/helpKnowledge.generated.ts b/apps/desktop/src/main/maker-ipc/helpKnowledge.generated.ts
index 904f12b334..cad905b636 100644
--- a/apps/desktop/src/main/maker-ipc/helpKnowledge.generated.ts
+++ b/apps/desktop/src/main/maker-ipc/helpKnowledge.generated.ts
@@ -16,7 +16,7 @@ export const HELP_KNOWLEDGE: HelpKnowledgeDoc[] = [
title: "Appearance, theme, wallpaper and fonts",
summary: "Theme, theme family, wallpaper, fonts, sidebar styles, panel layout, and reply animation — all in Settings > Appearance.",
tab: "appearance",
- content: "Settings > Appearance controls how the app looks. It starts with the theme and appearance mode, followed by Wallpaper, Fonts, Sidebar & panels, and Reply Animation. Display language and notifications stay in Settings > General (see the language and notifications topic).\n\n- **Theme**: pick from the registered theme families; each family supplies its own colors for light and dark. The app uses a VSCode-style token system (see docs/design-rules/cindy-design-system.md) so themes only override what they need. Families with only one variant are tagged Light only / Dark only; while one is selected the appearance mode is fixed to that variant, and your saved mode returns when you pick a two-variant theme.\n- **Appearance mode**: light, dark, or system (follows your OS).\n- **Wallpaper**: choose a Cindy scene, your own image, or a video for the whole app. The wallpaper is independent of the theme.\n- **Fonts**: choose fonts and sizes for interface text and code. Code font size changes code blocks, change comparisons, and editors; inline code, status numbers, badges, and path labels keep their size.\n- **Pinned Style**: show pinned sessions as Text, Cards, or List. **List Style** controls unpinned sessions: Text uses one line; List adds a preview.\n- **Local theme brand identity**: this is an optional power-user feature configured in the local theme JSON. The settings page intentionally keeps only create-copy, open-folder, and refresh actions. New copies include self-explanatory example paths directly in the JSON.\n- **Export / open local theme files**: export the current theme's tokens to a file or open a local theme JSON for inspection / sharing. To replace the icon and logo used on the new-chat page:\n\n ```json\n {\n \"brand\": {\n \"icon\": \"/absolute/path/to/your-image-folder/icon-square-50x50px.png\",\n \"logo\": \"/absolute/path/to/your-image-folder/logo-horizontal-110x37.5px.png\"\n }\n }\n ```\n\n The example filenames describe the final display areas; source images may be exported at 2x/3x while keeping the same aspect ratios. Paths must be absolute JSON strings; spaces do not need shell quotes. PNG, JPEG, and WebP are supported. Transparent padding is trimmed at render time without changing the source file. Only `brand.icon` and `brand.logo` are recognized; the previous single-image fields are not compatible with the redesigned two-asset layout.\n\n- **Plugin panel restore entry**: choose whether minimized plugin panels come back from a floating bubble or from the sidebar.\n- **Panel layout**: panel positions and widths are saved automatically; **Restore default layout** puts them back.\n- **Reply Animation**: new reply text fades in while it streams. Turn it off to show text immediately. It stays off when your system reduces motion.\n\n**Notes:**\n\n- Theme changes apply immediately; no restart needed.",
+ content: "Settings > Appearance controls how the app looks. It starts with the theme and appearance mode, followed by Wallpaper, Fonts, Sidebar & panels, and Reply Animation. Display language and notifications stay in Settings > General (see the language and notifications topic).\n\n- **Theme**: pick from the registered theme families; each family supplies its own colors for light and dark. The app uses a VSCode-style token system (see docs/design-rules/cindy-design-system.md) so themes only override what they need. Families with only one variant are tagged Light only / Dark only; while one is selected the appearance mode is fixed to that variant, and your saved mode returns when you pick a two-variant theme.\n- **Appearance mode**: light, dark, or system (follows your OS).\n- **Wallpaper**: choose a Cindy scene, your own image, or a video for the whole app. The wallpaper is independent of the theme.\n- **Fonts**: choose fonts and sizes for interface text and code. Code font size changes code blocks, change comparisons, and editors; inline code, status numbers, badges, and path labels keep their size.\n- **Pinned Style**: show pinned sessions as Text, Cards, or List. **List Style** controls unpinned sessions: Text uses one line; List adds a preview.\n- **Local theme brand identity**: this is an optional power-user feature configured in the local theme JSON. The settings page intentionally keeps only create-copy, open-folder, and refresh actions. New copies include self-explanatory example paths directly in the JSON.\n- **Export / open local theme files**: export the current theme's tokens to a file or open a local theme JSON for inspection / sharing. To replace the icon and logo used on the new-chat page:\n\n ```json\n {\n \"brand\": {\n \"icon\": \"/absolute/path/to/your-image-folder/icon-square-50x50px.png\",\n \"logo\": \"/absolute/path/to/your-image-folder/logo-horizontal-110x37.5px.png\"\n }\n }\n ```\n\n The example filenames describe the final display areas; source images may be exported at 2x/3x while keeping the same aspect ratios. Paths must be absolute JSON strings; spaces do not need shell quotes. PNG, JPEG, and WebP are supported. Transparent padding is trimmed at render time without changing the source file. Only `brand.icon` and `brand.logo` are recognized; the previous single-image fields are not compatible with the redesigned two-asset layout.\n\n- **Panel layout**: panel positions and widths are saved automatically; **Restore default layout** puts them back.\n- **Reply Animation**: new reply text fades in while it streams. Turn it off to show text immediately. It stays off when your system reduces motion.\n\n**Notes:**\n\n- Theme changes apply immediately; no restart needed.",
},
{
id: "attachments",
@@ -40,7 +40,7 @@ export const HELP_KNOWLEDGE: HelpKnowledgeDoc[] = [
id: "connections",
title: "Connecting external accounts",
summary: "External accounts (Google, Jira / Confluence, GitHub, GitLab) are connected on their plugin detail pages under Plugins; Slack and Telegram are bound under Settings > IM bots; Codex sign-in lives in Settings > Model Providers.",
- content: "External account connections have moved out of the old \"Third-Party Platforms\" section — each integration now lives on its own plugin detail page under **Plugins**, and the plugin's tools use the account you connect there.\n\n**Where to connect what:**\n\n- **Slack** — connect under **Settings > IM bots** (the \"Cindy\" tab). Each workspace has **Slack Communications on This Device** (本机 Slack 通讯) when the server supports it. Multiple authorized devices can search, read, and post as the Slack user, while only one device receives Bot chats and tasks. Turning off local communications does not revoke the account or affect other devices. Enabling communications on a previously displaced device may open Slack authorization, but never takes over the Bot. Old servers retain the original binding-based behavior.\n- **Telegram** — under **Settings > IM bots** (the \"Cindy\" tab), turn on Telegram and choose **Link Telegram**. Open the one-time link, start the official Cindy bot, and complete confirmation if prompted. The same card lets you cancel, retry, open the bot, add it to a group, or unlink; no personal bot token is required.\n- **Google** (Gmail / Calendar / Drive / Sheets) — handled by the Filo Google plugin (Plugins > Filo Google).\n- **GitHub** — handled by the Cindy GitHub plugin (Plugins > Cindy GitHub; existing PAT connections are migrated automatically). This connection is optional for `/issue`: feedback uses Cindy's official bot by default, and a working GitHub connection only adds the option to submit as yourself.\n- **GitLab** — handled by the Cindy GitLab plugin (Plugins > Cindy GitLab; existing PAT connections are migrated automatically).\n- **Codex** — sign in under Settings > Model Providers (separate from the Codex CLI binary the app ships with).\n- **FeiShu** — bot only (App ID / Secret under Settings > IM bots; see the FeiShu bot topic). FeiShu is no longer a sign-in method for Cindy itself.\n- **Cindy AI** — Settings > Model Providers. Web-search keys are configured on the matching plugin detail page (Cindy Web Search).\n\n**Managing connections:**\n\n- Each plugin detail page shows the connected accounts (with status) and lets you reconnect, disconnect, or switch the default account.\n- Disconnect removes the local token only; you may also want to revoke access on the provider's side.\n- A connection error usually means the token expired or was revoked on the provider's side; reconnect to refresh.",
+ content: "External account connections have moved out of the old \"Third-Party Platforms\" section — each integration now lives on its own plugin detail page under **Plugins**, and the plugin's tools use the account you connect there.\n\n**Where to connect what:**\n\n- **Slack** — connect under **Settings > IM bots** (the \"Cindy\" tab). Each workspace has **Slack Communications on This Device** (本机 Slack 通讯) when the server supports it. Multiple authorized devices can search, read, and post as the Slack user, while only one device receives Bot chats and tasks. Turning off local communications does not revoke the account or affect other devices. Enabling communications on a previously displaced device may open Slack authorization, but never takes over the Bot. Old servers retain the original binding-based behavior.\n- **Telegram** — under **Settings > IM bots** (the \"Cindy\" tab), turn on Telegram and choose **Link Telegram**. Open the one-time link, start the official Cindy bot, and complete confirmation if prompted. The same card lets you cancel, retry, open the bot, add it to a group, or unlink; no personal bot token is required.\n- **Google** (Gmail / Calendar / Drive / Sheets) — handled by the Filo Google plugin (Plugins > Filo Google).\n- **GitHub** — handled by the Cindy GitHub plugin (Plugins > Cindy GitHub; existing PAT connections are migrated automatically). This connection is optional for `/issue`: feedback uses Cindy's official bot by default, and a working GitHub connection only adds the option to submit as yourself.\n- **GitLab** — handled by the Cindy GitLab plugin (Plugins > Cindy GitLab; existing PAT connections are migrated automatically).\n- **Codex** — sign in under Settings > Model Providers (separate from the Codex CLI binary the app ships with).\n- **FeiShu** — bot only (App ID / Secret under Settings > IM bots; see the FeiShu bot topic). FeiShu is no longer a sign-in method for Cindy itself.\n- **Cindy AI** — Settings > Model Providers. Cindy Web Search uses this account by default and needs no key; optional Brave / Tavily / DeepSeek search keys are configured on that plugin's detail page.\n\n**Managing connections:**\n\n- Each plugin detail page shows the connected accounts (with status) and lets you reconnect, disconnect, or switch the default account.\n- Disconnect removes the local token only; you may also want to revoke access on the provider's side.\n- A connection error usually means the token expired or was revoked on the provider's side; reconnect to refresh.",
},
{
id: "feishu-bot",
@@ -107,14 +107,14 @@ export const HELP_KNOWLEDGE: HelpKnowledgeDoc[] = [
title: "Plugins (extending what the agents can do)",
summary: "What plugins are, how to browse / install / enable / disable them, per-working-directory control, the permission model, and invoking one with a $command.",
tab: "ghosts",
- content: "Plugins (internally \"意识\" / Ghost) extend what the agents can do — they add AI-callable tools, dockable UI panels, and \"ask Cindy to make it\" media generation. Each plugin is a self-contained `.cindy` capability pack that runs in its own isolated sandbox.\n\n**The Plugins page:**\n\n- Open it from the **Plugins** entry in the left sidebar.\n- Browse by origin: **all / built-in / team-shared / external**. The team-shared (enterprise) group only shows if your account belongs to an organization.\n- Each plugin has a detail page — that's where you enable it, connect an account / enter an API key, and read what it can do.\n\n**Built-in plugins that ship with the app:**\n\n- **Cindy Art** (`$cindy-art`) — generate and edit images and short videos.\n- **Cindy Web Search** (`$cindy-web-search`) — public web search (add your own Brave or Tavily key on its detail page).\n- **Cindy Mermaid** (`$cindy-mermaid`) — build / repair Mermaid diagrams.\n- **Cindy GitHub** (`$cindy-github`) / **Cindy GitLab** (`$cindy-gitlab`) — read / write issues, PRs / MRs, reviews, CI, releases.\n- **Filo Google** (`$filo-google`) — Gmail / Calendar / Drive / Sheets.\n\n**Enabling and disabling:**\n\n- **Enable / disable (globally)** from the plugin's detail page. Disabling puts its tools and panel to sleep but keeps the plugin installed — its layout position is remembered and restored when you re-enable it.\n- **Disable for one working directory only** — a plugin can be turned off just for a specific project. In that project's sessions it behaves as if it isn't installed (its tools and `$command` are unavailable there); everywhere else it stays on.\n\n**Installing:**\n\n- Install from the marketplace, or add a `.cindy` file manually (drag it in / pick it from disk).\n- Choosing Install, dragging a package, or picking one from disk first shows a **confirmation dialog** listing everything the plugin declares it can do (network domains, credentials, background tasks, skills, bundled code, panels…). Nothing is installed until you confirm; after that the plugin is enabled right away.\n- When you ask an agent to install a plugin (`ghost_market_install` / `ghost_forge_install`), the same confirmation appears as a card in that task — whatever the task's permission mode, including Full Access. It also works from the phone when you control this computer remotely. If you deny it, nothing is installed.\n- Plugins pushed by your organization (server default installs) are installed and updated silently without a confirmation.\n- The server selects the release appropriate for this Cindy version before marketplace delivery. Desktop does not apply a second `minCindyVersion` gate; custom marketplaces and local `.cindy` packages follow the same install policy.\n- Updates from stable marketplace sources are applied automatically when the plugin is idle — **as long as the new version doesn't need more permissions**. If it does, the automatic update pauses, the old version keeps working, and the plugin card shows \"New permissions need confirmation\"; clicking Update shows the added permissions for you to confirm. Failed attempts retry later; you can still click Update to retry immediately.\n\n**Creating or updating your own plugin:**\n\n- Choose **Create with Cindy** from the Plugins page's add menu. Cindy opens a new-task draft with the built-in Plugin Creator's actual command, selecting the built-in version even if a user Skill has the same name. Describe what you want and send it using your chosen Agent and model.\n- The built-in `cindy-plugin-creator` Skill supports creating, editing, debugging, packaging, and publishing plugins. Its bundled references contain the authoring documentation for the current Cindy version. If it is unavailable, the page reports that and keeps your existing draft.\n- Creating and packaging a plugin produces a `.cindy` file. Installation and publication are separate actions that you can request when ready.\n\n**Using a plugin with `$command`:**\n\n- Type its command at the **start** of a message — e.g. `$cindy-art a poster for…`. Only enabled plugins that declare that command match.\n- You don't have to use `$command`: the agents can also pick an enabled plugin's tools on their own when a task calls for it.\n\n**The permission / sandbox model (why plugins are safe):**\n\n- A plugin's sandbox has **no direct filesystem, network, or system access**. The host mediates every operation and enforces its actual execution context.\n- Autonomous/background plugin behavior must stay within the capabilities and scopes declared directly in its manifest. Whether an in-flight plugin tool runs is decided by the existing Agent authorization flow; network and working-directory operations bind to that call, while bundled code and CLIs continue to use the existing Node worker. Plugin authors do not need a client change or a manifest Slot to pre-register a specific command, host, or path.\n- **Autonomous network** access is limited to a domain allowlist the plugin declares; the host proxies every request. Credentials never enter the sandbox — the host injects them only into declared requests whose target matches that declaration.\n- Because of this, a plugin **can't see your files** on its own. A file reaches a plugin only when you or the agent explicitly hand one over (an image attachment, or a directory the host passes through after an ownership check).\n\n**Configuring a plugin's account / API key:**\n\n- Do it on the plugin's **detail page**. Plugins that use a key (web-search, GitHub/GitLab tokens) have a field there; the value goes straight into the host's encrypted store and can't be read back.\n- Plugins that use OAuth (for example Filo Google) show a **Connect account** button instead.\n\n**Notes:**\n\n- Enabling or disabling a plugin takes effect on the **next** agent query, not retroactively in the current turn.\n- Skills (`/` slash commands) and Plugins (`$` commands) are two tabs of the same management surface — see the Skills topic for skills.",
+ content: "Plugins (internally \"意识\" / Ghost) extend what the agents can do — they add AI-callable tools, panels that live as pinned tabs in the right sidebar, full-page app views, and \"ask Cindy to make it\" media generation. Each plugin is a self-contained `.cindy` capability pack that runs in its own isolated sandbox.\n\n**The Plugins page:**\n\n- Open it from the **Plugins** entry in the left sidebar.\n- Browse by origin: **all / built-in / team-shared / external**. The team-shared (enterprise) group only shows if your account belongs to an organization.\n- Each plugin has a detail page — that's where you enable it, connect an account / enter an API key, and read what it can do.\n\n**Built-in plugins that ship with the app:**\n\n- **Cindy Art** (`$cindy-art`) — generate and edit images and short videos.\n- **Cindy Web Search** (`$cindy-web-search`) — public web search. **No key needed**: by default it searches through Cindy AI and uses your signed-in Cindy account's balance (unavailable in local mode). Results come with a title, link, and short summary. To search through your own service instead, add a Brave, Tavily, or DeepSeek key on its detail page. A failed search is reported as-is; it never silently switches to another source.\n- **Cindy Mermaid** (`$cindy-mermaid`) — build / repair Mermaid diagrams.\n- **Cindy GitHub** (`$cindy-github`) / **Cindy GitLab** (`$cindy-gitlab`) — read / write issues, PRs / MRs, reviews, CI, releases.\n- **Filo Google** (`$filo-google`) — Gmail / Calendar / Drive / Sheets.\n\n**Enabling and disabling:**\n\n- **Enable / disable (globally)** from the plugin's detail page. Disabling puts its tools and panel to sleep but keeps the plugin installed — its right-sidebar tab is kept and comes back when you re-enable it. A plugin's panel shows up as a pinned tab in the right sidebar that stays across tasks; close it from the tab, and reopen it later by right-clicking the plugin's entry in the left sidebar and choosing \"Open in the sidebar\".\n- **Disable for one working directory only** — a plugin can be turned off just for a specific project. In that project's sessions it behaves as if it isn't installed (its tools and `$command` are unavailable there); everywhere else it stays on.\n\n**Installing:**\n\n- Install from the marketplace, or add a `.cindy` file manually (drag it in / pick it from disk).\n- Choosing Install, dragging a package, or picking one from disk first shows a **confirmation dialog** listing everything the plugin declares it can do (network domains, credentials, background tasks, skills, bundled code, panels…). Nothing is installed until you confirm; after that the plugin is enabled right away.\n- When you ask an agent to install a plugin (`ghost_market_install` / `ghost_forge_install`), the same confirmation appears as a card in that task — whatever the task's permission mode, including Full Access. It also works from the phone when you control this computer remotely. If you deny it, nothing is installed.\n- Plugins pushed by your organization (server default installs) are installed and updated silently without a confirmation.\n- The server selects the release appropriate for this Cindy version before marketplace delivery. Desktop does not apply a second `minCindyVersion` gate; custom marketplaces and local `.cindy` packages follow the same install policy.\n- Updates from stable marketplace sources are applied automatically when the plugin is idle — **as long as the new version doesn't need more permissions**. If it does, the automatic update pauses, the old version keeps working, and the plugin card shows \"New permissions need confirmation\"; clicking Update shows the added permissions for you to confirm. Failed attempts retry later; you can still click Update to retry immediately.\n\n**Creating or updating your own plugin:**\n\n- Choose **Create with Cindy** from the Plugins page's add menu. Cindy opens a new-task draft with the built-in Plugin Creator's actual command, selecting the built-in version even if a user Skill has the same name. Describe what you want and send it using your chosen Agent and model.\n- The built-in `cindy-plugin-creator` Skill supports creating, editing, debugging, packaging, and publishing plugins. Its bundled references contain the authoring documentation for the current Cindy version. If it is unavailable, the page reports that and keeps your existing draft.\n- Creating and packaging a plugin produces a `.cindy` file. Installation and publication are separate actions that you can request when ready.\n\n**Using a plugin with `$command`:**\n\n- Type its command at the **start** of a message — e.g. `$cindy-art a poster for…`. Only enabled plugins that declare that command match.\n- You don't have to use `$command`: the agents can also pick an enabled plugin's tools on their own when a task calls for it.\n\n**The permission / sandbox model (why plugins are safe):**\n\n- A plugin's sandbox has **no direct filesystem, network, or system access**. The host mediates every operation and enforces its actual execution context.\n- Autonomous/background plugin behavior must stay within the capabilities and scopes declared directly in its manifest. Whether an in-flight plugin tool runs is decided by the existing Agent authorization flow; network and working-directory operations bind to that call, while bundled code and CLIs continue to use the existing Node worker. Plugin authors do not need a client change or a manifest Slot to pre-register a specific command, host, or path.\n- **Autonomous network** access is limited to a domain allowlist the plugin declares; the host proxies every request. Credentials never enter the sandbox — the host injects them only into declared requests whose target matches that declaration.\n- Because of this, a plugin **can't see your files** on its own. A file reaches a plugin only when you or the agent explicitly hand one over (an image attachment, or a directory the host passes through after an ownership check).\n\n**Configuring a plugin's account / API key:**\n\n- Do it on the plugin's **detail page**. Plugins that use a key (optional search-service keys for Web Search, GitHub/GitLab tokens) have a field there; the value goes straight into the host's encrypted store and can't be read back.\n- Plugins that use OAuth (for example Filo Google) show a **Connect account** button instead.\n\n**Notes:**\n\n- Enabling or disabling a plugin takes effect on the **next** agent query, not retroactively in the current turn.\n- Skills (`/` slash commands) and Plugins (`$` commands) are two tabs of the same management surface — see the Skills topic for skills.",
},
{
id: "providers",
title: "Model providers and Cindy AI",
summary: "Cindy AI is auto-provisioned after sign-in for pay-per-token model access; manage it (and custom providers) in Settings > Model Providers.",
tab: "providers",
- content: "Claude Code, Codex, and lightweight utility models can use **Cindy AI** for pay-per-token model access. Voice input is included for signed-in Cindy users and uses the separate voice service; it does not require or receive a Cindy AI key.\n\n**Cindy AI:**\n\n- Open **Settings > Model Providers** (the tab is labeled \"Providers\"). Cindy AI is pinned at the top.\n- You don't paste a key — it's **provisioned automatically after you sign in**. The page fetches its credentials for you (\"Fetching credentials…\" while it does).\n- Controls: **Refresh credentials**, **Rotate key**, and **Disconnect** (which clears the Cindy AI key saved locally). Because it's tied to your account, it's available on each device you sign into.\n\n**Status badges:**\n\n- **Connected** — this device has usable Cindy AI credentials.\n- If it's still fetching or disconnected, use Refresh credentials / sign in.\n\n**Custom providers:**\n\n- You can also add your own provider (a base URL + key) — that's the flow with a paste-a-key dialog. Cindy AI itself never uses that dialog.\n\n**Notes:**\n\n- Direct service keys such as Brave Search and Tavily are **not** managed here — they live on the matching plugin detail pages under Plugins (Cindy Web Search).\n- Rotating or replacing credentials takes effect for new turns; in-flight requests finish on the previous key.",
+ content: "Claude Code, Codex, and lightweight utility models can use **Cindy AI** for pay-per-token model access. Voice input is included for signed-in Cindy users and uses the separate voice service; it does not require or receive a Cindy AI key.\n\n**Cindy AI:**\n\n- Open **Settings > Model Providers** (the tab is labeled \"Providers\"). Cindy AI is pinned at the top.\n- You don't paste a key — it's **provisioned automatically after you sign in**. The page fetches its credentials for you (\"Fetching credentials…\" while it does).\n- Controls: **Refresh credentials**, **Rotate key**, and **Disconnect** (which clears the Cindy AI key saved locally). Because it's tied to your account, it's available on each device you sign into.\n\n**Status badges:**\n\n- **Connected** — this device has usable Cindy AI credentials.\n- If it's still fetching or disconnected, use Refresh credentials / sign in.\n\n**Custom providers:**\n\n- You can also add your own provider (a base URL + key) — that's the flow with a paste-a-key dialog. Cindy AI itself never uses that dialog.\n\n**Notes:**\n\n- Direct service keys such as Brave Search, Tavily, and DeepSeek search are **not** managed here — they live on the matching plugin detail pages under Plugins (Cindy Web Search). They are optional; web search works through Cindy AI without them.\n- Rotating or replacing credentials takes effect for new turns; in-flight requests finish on the previous key.",
},
{
id: "remote",