> 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/zhi-shi-zheng-li-yu-zi-liao-shou-ji/digests.md).

# 跨站彙整

彙整（Digests）是口袋瀏覽器的全域知識檢索中心，將所有網頁累積的摘要、摘錄與任務集中索引。

***

## 為什麼需要彙整

在深度研究過程中，使用者會在不同網站記錄各自的摘要或文字摘錄。若缺乏統一彙整介面，這些知識碎片將隨著分頁關閉而被遺忘在龐大的歷史紀錄中。

「彙整」頁籤充當個人知識庫的全文搜尋引擎：

* 將使用者在各分頁記下的「摘要」（網頁核心意義）、「摘錄」（選取文字與註解）以及「任務」全部歸納在一起。
* 提供單一搜尋框，輸入關鍵字即可即時跨網頁檢索相關知識點。

***

## 核心功能

### 1. 統一跨站檢索

* 搜尋欄支援多關鍵字即時比對。
* 結果即時呈現關聯的摘要短評、原文摘錄片段與任務標題。

### 2. 溯源與無縫導航

* 每個彙整結果均附帶原始網站圖示、網域名稱與建立時間。
* 點擊任一結果卡片：
  * 若目標網頁仍開啟於分頁中，瀏覽器直接切換該分頁。
  * 若目標網頁已關閉，瀏覽器自動於右側開啟新分頁並導航至原始網址。

### 3. 分類過濾

支援依資料類型（僅看任務、僅看摘錄、僅看摘要）或依來源網站網域進行快速分類過濾。


---

# 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/zhi-shi-zheng-li-yu-zi-liao-shou-ji/digests.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.
