# dsh-tree-view
**TreeView — use a conversation as a tree**
[简体中文](README.md) | English
Edit an old message and the conversation forks from that turn; every version lives in one tree, and the sidebar keeps a single entry.
[](https://www.npmjs.com/package/dsh-tree-view)
[](./LICENSE)
[](#install)
[](#versions-and-compatibility)
[](#contributing)
[](https://github.com/Rice00/dsh-tree-view/stargazers)
---
**Edit a message you already sent**, or use DSH's own **Branch into a new conversation** button — either way it grows a new branch here:
Switch the conversation panel to Tree and the whole family is drawn on one canvas:
## Features
| Feature | What it does |
|---|---|
| 🖱️ **Jump to a branch** | Every node is a real session version; clicking it moves you onto that line. Underneath it is only an archived flag being flipped: the version you clicked is unarchived back into the sidebar, and the one you were reading is archived into the tree — so moving around the tree moves the sidebar slot rather than adding to it. |
| 🔀 **Parallel lines** | A version *is* a session. Right-click and send several of them "back into the main chat" — that step only unarchives, it touches nothing else — and two branches can work at the same time without disturbing each other; collect them again when you are done. |
| 🧹 **One-click collect** | The panel toolbar's "collect every other branch" gathers the family's strays into the tree at once, leaving the one you are using. If any of them is still generating a reply it asks first — stop and collect, or cancel — so nothing is killed quietly. |
| 🗂️ **Folding** | A run of turns with no fork in it — the opening every version shares included — folds into a single node once it reaches the configured length; click to unfold. The threshold is chosen in Settings, the toolbar folds it back at any time, and the view re-frames itself after either. |
| 🚫 **Hiding empty forks** | Forks that only copied this conversation without adding a turn of their own are not drawn; the toolbar carries the same switch. |
| ✏️ **Renaming branches** | Right-click a node to name a branch. The sidebar title stays the host's own (`(1)`, `(2)` and all) — only the box drawn in the tree is named. |
| 🔄 **Version ring** | The `‹ n/m ›` ring under a message, to move between versions of the same question without leaving the chat. |
| 🎯 **Highlighted reading path** | The whole line you are reading — shared opening included — is highlighted on the canvas, so where you came from, where you are and where you can still go read off one picture. |
| 📌 **Resume where you left off** | Coming back to this family from another conversation resumes the version you last read (off by default; switchable in Settings). |
| 🤖 **Subagent tags** | A subagent session hanging under this conversation carries a tag, so it is not read as one of your versions. |
| 📦 **Archived branches stay** | A version you archive is still drawn, dimmed and marked "archived" — archiving takes an entry out of the sidebar, it does not delete a branch. |
| 🎨 **Following the theme** | Surface, border, accent, state and even shadow colours come from the host's theme tokens: light follows light, dark follows dark. |
## How it works
| Point | Detail |
|---|---|
| **A rewind, not a continuation** | When you edit, the host seeds a new session with every event before that turn and sends the edited prompt into it — the new version restarts from the sentence you changed, with the same working directory and context. DSH's own "Branch into a new conversation" produces the same kind of history-seeded session, and the plugin reads its fork point off the seed length just the same. |
| **Old versions survive** | The original line is still in the tree; one click goes back to it, and both lines can keep going independently. |
| **Nothing collects on your behalf** | Editing, retrying, opening a session from the sidebar and restoring where you last read change no archived flag at all — only picking a version from the tree, or pressing "collect every other branch", does. Otherwise one casual rewording would quietly collect the session you were in. |
## Legend
| On the canvas | What it is |
|---|---|
| The trunk | The opening every version shares — the turns before the first fork |
| A fork | One edit: one side is the original, the other is the rewritten version |
| The highlighted line | The version you are reading, from the start of the conversation to the turn on screen |
| A stack of sheets | A run of consecutive turns folded together |
Pan, zoom with the wheel, click a node to jump there; right-click a node to rename it or to decide whether it lives in the sidebar or in the tree.
## Archive and restore
Archiving is the only switch this plugin touches on your data, so it gets its own section:
- **Into the tree** archives that version out of the DSH sidebar; **back into the main chat** unarchives it. This DSH build ships no unarchive API, so the plugin writes that state the way the archive registry itself does — all of it in `lib/archive-adapter.js`, probed at startup: whatever the host is missing is logged, the affected buttons grey out, and the rest of the tree keeps working.
- **Nothing is deleted, copied or rewritten.** The session log is append-only, and apart from the one `message-tree/version` marker a fork has to write, the plugin adds nothing to it.
- **After uninstalling**, every session is still there; the versions that were collected into the tree can be unarchived from DSH's own archive list. Branch names and "who was collected" live in `~/.dsh/storages/tree-view/state.json` — harmless to keep, and deleting it does not affect any session.
## Install
Install from npm:
```bash
dsh plugin --profile web add dsh-tree-view
```
Or straight from GitHub:
```bash
dsh plugin --profile web add github:Rice00/dsh-tree-view
```
The patch inserts one row (`tree-view`) into the profile. Then **restart that profile** — host plugin modules are cached in-process, so a running harness will not pick the new row up; UI-only changes just need a page refresh.
Or install a local checkout, to have edits take effect immediately (`link:` is a live link, and the folder must not move afterwards):
```bash
git clone https://github.com/Rice00/dsh-tree-view.git
dsh plugin --profile web add link:/abs/path/to/dsh-tree-view
```