> For the complete documentation index, see [llms.txt](https://doc.qrspace.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.qrspace.dev/he-xin-kong-jian-jia-gou/workspaces.md).

# 多工作區與任務隔離

口袋瀏覽器內建多工作區（Workspaces）機制，讓不同專案的分頁與上下文完全隔離，避免視窗分頁氾濫。

***

## 為什麼需要多工作區

在日常工作與深度調研中，使用者常同時處理多項獨立任務（例如：專案代碼調試、客戶信件回覆、技術文件閱讀）。若全部混在同一排分頁列，不僅容易誤關分頁，注意力也容易被非關聯分頁干擾。

口袋瀏覽器的工作區讓每個專案擁有獨立的分頁組、獨立的瀏覽紀錄與獨立的工作狀態。

***

## 操作與切換方式

### 1. 快捷鍵快速切換

* 使用 `Ctrl + Alt + ←` 切換至左側相鄰工作區。
* 使用 `Ctrl + Alt + →` 切換至右側相鄰工作區。 切換過程無延遲，後台未啟動的分頁自動休眠，節省記憶體。

### 2. 分頁跨區搬移

在分頁列上，可直接將分頁標籤拖曳至工作區導航點上。釋放滑鼠後，該分頁即被指派至目標工作區，自動從當前工作區分頁列中移出。

### 3. 工作區獨立狀態

每個工作區具備以下特性：

* **獨立分頁棧**：分頁列僅顯示當前工作區的分頁。
* **獨立路徑圖紀錄**：路徑圖（Trail View）會以當前工作區為單位進行主線與分支分析。
* **狀態持久化**：重啟瀏覽器後，各工作區的分頁排列與歷史順序完全還原。


---

# 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://doc.qrspace.dev/he-xin-kong-jian-jia-gou/workspaces.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.
