> 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/clipboard-history.md).

# 500 則剪貼簿歷史

口袋瀏覽器內建高容量剪貼簿歷史管理器，完整保留最近 500 筆複製紀錄。

***

## 為什麼需要 500 則剪貼簿歷史

在資料蒐集、文案編寫與代碼調試過程中，使用者常需要頻繁在多個網頁之間複製不同段落。系統預設剪貼簿一次只能保留一筆內容，新的複製動作會無情覆蓋舊內容，迫使使用者反覆來回切換分頁重新複製。

口袋瀏覽器提供 500 則深度歷史快取：

* 任何在瀏覽器內（或系統中）複製的文字，均自動依時間序列寫入快取清單。
* 深度達 500 筆，避免數小時前複製過的關鍵片段被過早覆蓋。

***

## 核心操作與隱私控制

### 1. 快速檢索與重複貼上

* 在側邊欄切換至剪貼簿頁籤，或透過快捷鍵叫出剪貼簿面板。
* 頂部搜尋列支援全文檢索，可輸入片段字詞快速過濾歷史紀錄。
* 點擊任一紀錄項目即可重新置入系統剪貼簿，或直接拖曳填入輸入框。

### 2. 資料類型支援

* 支援純文字（Plain Text）、格式化文本（Rich Text）、程式碼片段與連結。
* 程式碼段落自動標註換行與縮排，避免排版錯亂。

### 3. 金庫敏感資訊保護

為防範帳號密碼外洩，從內建密碼金庫複製的密碼具有自動保護機制：30 秒後若系統剪貼簿依然為該密碼內容，系統將自動將其清除，且密碼項目不會留存在 500 則剪貼簿歷史中。


---

# 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/clipboard-history.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.
