> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/zhong-wen-fan-ti/advanced-basic/workbench.md).

# 高效工作台

多窗口、輸入工具同全局搜尋

Cherry Studio 嘅主視窗由側邊欄、分頁同內容區組成。對話話題同 Agent 任務可以同時喺多個分頁開住，亦可以拆做獨立視窗；輸入區工具欄就可以按使用習慣調整。

<figure><img src="https://2742912793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Ut5BptC3t8CtSU1UWpM%2Fuploads%2FndicNnbnZ4ToE8Y0KI8e%2Fclipboard.png?alt=media&amp;token=d71894d2-66c9-4640-8b88-ff5b1e5d3b14" alt="标签页右键菜单中的固定标签页、从新窗口打开和关闭其他标签页"><figcaption><p>需要同時睇資料同任務時，可以將其中一個分頁喺新視窗打開，主視窗繼續保留全局線索。</p></figcaption></figure>

### 適合用獨立視窗嘅場景

* 一邊保留資料對話，一邊運行 Agent 任務；
* 將長期監控任務置頂，避免俾其他視窗遮擋；
* 喺唔同顯示器上分別擺對話、文件或者任務；
* 展示或分享某個任務時，唔暴露主視窗入面其他分頁。

### 工作台功能

| 能力    | 入口                  | 作用              |
| ----- | ------------------- | --------------- |
| 新分頁   | 話題或任務右鍵選單→【喺新分頁中打開】 | 喺主視窗入面並排保留多個上下文 |
| 獨立視窗  | 話題、任務或分頁右鍵→【從新視窗打開】 | 將當前內容拆去新視窗      |
| 置頂分頁  | 分頁右鍵→【固定分頁】         | 固定常用頁面          |
| 視窗置頂  | 獨立視窗頂部【視窗置頂】        | 令任務保持可見         |
| 返回主視窗 | 獨立視窗頂部【返回主視窗】       | 將分頁重新接返主視窗      |
| 自訂工具欄 | 輸入區【+】→【自訂工具欄】      | 調整常用輸入工具嘅位置     |

<figure><img src="https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=-699042616/https%3A%2F%2Ffiles.gitbook.com%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%2F0Ut5BptC3t8CtSU1UWpM%2Fuploads%2F8VMddiCgANblcfevpdmG%2Fclipboard.png%3Falt%3Dmedia%26token%3Dee731be7-6796-48e3-984d-f1db407c0707" alt="标签页菜单中的从新窗口打开操作"><figcaption><p>喺分頁選單入面揀【從新視窗打開】，就可以將當前內容拆去獨立視窗。</p></figcaption></figure>

### 推薦佈局

辦公寫作可以將資料對話留喺主視窗，將「寫作」Agent 拆去右邊屏幕；程式碼工作可以將 Agent 任務置頂，主視窗保留文件同文檔；長時間監控任務用獨立視窗，但唔好將需要頻繁確認權限嘅任務擺喺睇唔到嘅位置。

{% hint style="info" %}
獨立視窗仍然屬於同一個 Cherry Studio 數據環境。佢唔係新嘅帳號或者私隱空間；同一話題或任務嘅內容仍然會同步保存。
{% endhint %}

### 相關教學

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>多視窗同分頁</strong></td><td>拆分、置頂同重新接返視窗</td><td></td></tr><tr><td><strong>輸入工具欄同效率工具</strong></td><td>提示詞管理、快捷鍵、快捷助手同劃詞助手</td><td></td></tr><tr><td><strong>截圖、標註同 OCR</strong></td><td>跨應用截圖、脫敏同複製文字</td><td></td></tr></tbody></table>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>多視窗同分頁</strong></td><td>拆分、置頂同重新接返視窗</td><td><a href="/docs/zhong-wen-fan-ti/advanced-basic/workbench/multi-window-tabs.md">多窗口同標籤頁</a></td></tr><tr><td><strong>輸入工具欄同效率工具</strong></td><td>提示詞管理、快捷鍵、快捷助手同劃詞助手</td><td><a href="/docs/zhong-wen-fan-ti/advanced-basic/workbench/composer-efficiency.md">輸入工具欄同效率工具</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cherryai.com.cn/docs/zhong-wen-fan-ti/advanced-basic/workbench.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.