> 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/ce-bian-gong-ju-lie-yu-kuo-chong/trail-view.md).

# 路徑圖：視覺化瀏覽歷程

路徑圖是口袋瀏覽器的核心脈絡追蹤工具，將使用者的網頁瀏覽歷程轉化為直觀的視覺化時間軸。

***

## 介面實例

<div align="center"><img src="https://3201536177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnLOM9eEC6ENcPwwmJe6V%2Fuploads%2Fgit-blob-bc5035fcfb2e6ee74d4a713e64be1544c998d3bc%2Ftrail-view.png?alt=media" alt="路徑圖介面" width="800"></div>

***

## 為什麼需要路徑圖

多數使用者在查閱資料時，常面臨兩種困境：

1. **注意力分散**：從搜尋引擎點入 A 網站，途中被側邊推薦吸引點入 B、C 網站，不知不覺偏離初始研究目標。
2. **工作難以接續**：離開電腦數小時甚至數天後重新開機，面對幾十個分頁，難以辨識上次停在何處、哪一頁才是未完成的核心進度。

傳統歷史紀錄（History）僅以時間由新到舊倒序排列，無法呈現不同網頁之間的跳轉因果關係與停留時間。路徑圖即為解決此問題而設計。

***

## 核心功能解析

### 1. 一站一站的因果樹狀歷程

路徑圖自動追蹤網頁的起點與後續跳轉：

* 清楚呈現使用者從哪個搜尋引擎或入口網站開始瀏覽。
* 將同一主題下連續開啟的頁面串聯成「路徑鏈」，直觀辨識每站之間的依賴關係。

### 2. 主線與偏離分析

系統在時間軸上方自動統計專注比例：

* **主線任務時間**：例如當前主線專案「Stitch」累計瀏覽時間。
* **分支干擾分析**：精確標示偏離主線的其他瀏覽事件與時間長度。
* **離開時間統計**：記錄中途離開螢幕或視窗最小化的間隔（例如「離開 5 次，共 4 小時 34 分」），清楚掌握時間利用率。

### 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/ce-bian-gong-ju-lie-yu-kuo-chong/trail-view.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.
