feiyaochang123-sys/dsh-starred-turns

dsh-starred-turns

Bookmark turns from the conversation's right-edge turn rail — the column of short dashes where each dash marks one turn and jumps back to it when clicked. A bookmarked dash grows to the rail's full length and takes the accent colour, so a specific turn stays easy to find in a long conversation.

Right-click a dash to bookmark it; right-click again to unbookmark.

中文说明

Why

A long conversation gives you a rail of identical dashes. The shipped rail already distinguishes the active turn, but nothing lets you mark the turns you care about — the decision, the diff, the answer you keep scrolling back to. This plugin adds exactly that one bit per turn, and makes it visible at a glance by reusing the rail's own "full length" geometry.

Features

• Right-click to bookmark a turn. The dash grows from its resting length (scaleX 0.4 for turns not loaded into the transcript, 0.6 for loaded ones) to the rail's full width (scaleX 1), and switches from the neutral border colour to the accent colour.
• Bookmarks are per conversation. Turn 5 in one conversation and turn 5 in another are different places; the conversation key is the selected Session id.
• Bookmarks persist. They survive reloads and, on the Desktop build, app restarts.
• No layout shifts. The rail keeps its fixed 10px pitch; only the dash's own scaleX changes.

Install

dsh plugin add dsh-starred-turns

Or add it to a profile's cordis.patch.yml by hand:

- insert:
    - id: starred-turns
      name: dsh-starred-turns

Restart the app (or let HMR rescan) after installing: the Host only scans plugin packages at startup.

How it fits in without touching the chat package

The rail is drawn by @deepseek-ai/dsh-client-ui-chat and is not slot-extended, so the plugin decorates it from the outside rather than forking the package. Each dash is:

<button data-index="18" class="…_mark …_markActive" aria-label="Jump to turn 19"></button>

with the visible dash supplied by a ::before pseudo-element:

.…_mark:before          { width: 20px; height: 2px; transform: translateY(-50%) scaleX(.6); }
.…_markActive:before    { transform: translateY(-50%) scaleX(1); }
.…_markUnloaded:before  { transform: translateY(-50%) scaleX(.4); }

So the plugin does three things, all from the outside:

1. a capture-phase contextmenu listener on document toggles the bookmark for the dash under the pointer;
2. a MutationObserver (watching data-index and child insertion) plus a store subscription keep a data-dsh-starred-turn attribute painted on the right dashes;
3. its stylesheet turns that attribute into scaleX(1) in the accent colour.

Bookmarking deliberately reuses the dash's own scaleX geometry instead of changing width or height, which is what keeps the rail's pitch intact.

The observer never watches the plugin's own attribute — it writes that attribute, so an unguarded observer would retrigger itself forever. Paints are also guarded by a read of the current attribute for the same reason.

Storage

Bookmarks live in a client store named dsh.starred-turns.v1, keyed by conversation:

{ "byConversation": { "session-…": ["1", "7"] } }

The shell backs persist with localStorage. On the Desktop build the page origin is the stable dsh-app://app scheme, so bookmarks survive app restarts there. On a plain browser the Host picks a new loopback port per launch and browsers scope localStorage by origin including the port, so bookmarks do not carry across restarts in that mode.

Develop

npm install
npm run build   # src -> lib (client bundle in the shell's closure-factory format)
npm test        # bundle shape, exported surface, selector targets

• src/client.js — store, rail painting, right-click gesture, stylesheet
• src/index.js — node half (host-side no-op; exists so the Loader has an entry module)
• scripts/build.mjs — copies the node half and bundles the browser half with esbuild

License

MIT