Sent Message Locator (sent-msg-locator)

English · 中文

!GitHub Release !License !GitHub Stars 

A DSH (DeepSeek Harness) plugin that locates every turn of the current session (a turn = your message sent → assistant's complete reply).

A slim floating rail sits at the left edge of the conversation area: one bubble-shaped numbered badge per turn. Click a badge to smooth-scroll the chat viewport to the first user-typed message of that turn; the rail highlights the turn you are currently viewing and follows along as you scroll, updating in real time.

Since v2.2.0 this is a static bundle plugin loaded automatically from the profile layer stack — install once, and it activates on every DSH startup with no manual define/run needed.

Features

• Left-edge icon rail (fixed position, ~40px wide, always visible):

- One bubble-shaped numbered badge per turn (#N), latest turns at the bottom - Click a badge → smooth-scroll to the exact user-typed message of that turn (matched via the built-in chat anchor mechanism data-chat-anchor-key, element-level API, never touches document/window) - Current-turn highlight follows scrolling; the rail auto-scrolls to keep the highlighted badge visible - In-progress turns show a dashed translucent badge until the reply completes - Hover tooltip: a rounded custom card — "Turn N · time (· in progress)" plus the first user-typed message of that turn (clamped to 280px × 6 lines with an ellipsis; image-only messages show "[image]"); also shown on keyboard focus - Internal scrollbar for long conversations; rail stays at the left edge of the conversation area (right of the sidebar) and follows sidebar collapse/drag via timer-calibrated coordinates

• Turn unit: one official engine Turn (user send → assistant complete reply), including open/in-progress status
• Real-time updates: the rail refreshes as the session snapshot changes; switching sessions clears stale data automatically
• Theme aware: all colors use theme CSS variables (--dsw-alias-*), readable on light/dark/any theme

Data comes from the official chat.timeline (turnOrder + turns) merged with the chat.nodes snapshot (so turns never disappear when session history is paged via loadOlder). No backend dependency, no document/window manipulation.

> Pure Client plugin: no Host capabilities (no RPC / fs / network / spawn). Scrolling uses only element-level APIs (closest / getBoundingClientRect / scrollTo / scrollIntoView).

Demo


Click a badge to smooth-scroll to that turn's user-typed message; the current-turn highlight follows scrolling and updates in real time.

Quick Start

# Install (static bundle, recommended)
dsh plugin --profile web add sent-msg-locator

For a local, unpublished copy use file: pointing at this repository (the path must NOT contain spaces):

dsh plugin --profile web add file:/path/to/sent-msg-locator

Restart dsh web and the plugin activates automatically: the numbered rail appears at the left edge of the conversation area. No manual define/run required.

Usage

1. See the rail: open any session with history — a floating numbered rail appears at the left edge of the conversation area, one bubble badge per completed turn; 2. Jump to a turn: click any badge — the chat viewport smooth-scrolls to the first user-typed message of that turn; 3. Follow your position: scroll the conversation — the current-turn badge highlights (brand color) and the rail auto-scrolls to keep it visible; 4. Long conversations: scroll the rail's own scrollbar to browse all turns; older turns appear as you load more history (Load earlier in the chat view — the DSH engine pages history at 50 events per request, so earlier turns show up incrementally); 5. In-progress turns: while the assistant is replying, the newest badge is dashed/translucent and becomes clickable once the reply completes.

Repository Contents

Two Forms

> Do not activate the static bundle and the dynamic form at the same time — the same slots would be registered twice and the rail would render duplicated.

Dynamic fallback steps:

1. Have an agent read client-source.js; 2. cordis_define: plugin: { kind: "new", idPrefix: "smsg" }, name/purpose from manifest.json, code.host: null, code.client as the full content of client-source.js; 3. cordis_run to activate; success when the rail appears.

> The dynamic form does not survive DSH restarts and must be reloaded; the static bundle form has no such limitation.

Technical Notes

• Data source: useSession snapshot → official chat.timeline (turnOrder + turns) as primary, chat.nodes snapshot as fallback — merged so turns never go missing when session history is paged (loadOlder limits each page to 50 events). Per-turn fields: turn number / start.time / end.time / status (open / closed / unknown).
• Data bridge: a hidden 0-size element inside the session-scoped conversation.input.dock slot captures useSession/sessionId and measures the conversation-area left edge (getBoundingClientRect, element-level) as the fixed-position baseline; a 300ms timer poll keeps the rail attached to the sidebar's right edge when the sidebar collapses or is dragged.
• Turn-tail anchors: the additive conversation.chat.assistant-actions slot renders a 0-size anchor element at each completed assistant message, resolving its turn from the snapshot node's data.turn; the first anchor attaches a scroll listener on the chat scroll container (closest('[data-conversation-scroll]')) for current-turn detection.
• Precise jump: click → match the snapshot node key against the built-in data-chat-anchor-key rows (element-level querySelectorAll), compute the row position, smooth-scroll; falls back to the tail-anchor position when the row is missing.
• Current-turn detection: on scroll, the turn of the first anchor below the viewport top wins; the rail keeps the highlighted badge visible with scrollIntoView({ block: 'nearest' }).
• Hover tooltip card (v2.3.0): data comes from the first kind === 'user' / 'steering' node of the turn — data.content (ContentBlock[], only { type: 'text' } blocks are joined; image-only messages show "[image]" placeholder). Steering nodes are also user input: the session's first message (and mid-turn steering messages) are claimed via agent/inbox/spliced (target: next-step) and rendered as kind === 'steering' instead of 'user' (same renderer, same anchor mechanism — no visible difference; fixed in v2.3.2 so the first badge shows its text too). A custom fixed-position rounded card replaces the native title (which cannot be sized or rounded; aria-label keeps the summary): ≤280px wide, text clamped to 6 lines (-webkit-line-clamp + max-height fallback, plus a 400-code-point JS safety cap); clamped against the chat scroll container's getBoundingClientRect to avoid right/top/bottom overflow; a 200ms timer poll re-measures while shown (follows sidebar drag / rail internal scroll); rendered as a sibling of the rail (the rail has overflow-y: auto and would clip children); triggered by mouse hover and keyboard focus; pointer-events: none so it never blocks the badges.
• Paged window & placeholder (v2.3.3): history loads in pages of 50 messages (the page cut never splits a message but can split a turn), so the oldest visible turn (the rail's first badge — its number is not necessarily 1) usually has only its tail loaded — its user message lies outside the loaded window and no user/steering node exists in the snapshot, so the text cannot be obtained client-side. In that case the tooltip shows an italic placeholder "该轮用户消息尚未加载，点击聊天区「加载更早」后显示" (label-tertiary theme color); clicking "Load earlier" refreshes the snapshot and the text appears automatically.
• Compaction marker (v2.1.12): after DSH auto-compaction the old turns disappear from the rail; a small compaction icon + dashed separator appears at the top (detected via kind === 'compaction' checkpoint nodes), tooltip "N history records compressed · ~M tokens".
• All slots are additive (conversation.input.dock / conversation.chat.assistant-actions / shell.overlay); no built-in UI is replaced.

Security & Boundaries

• Capability declaration: none (pure UI) — no network requests, no spawn/process, no filesystem, no document/window globals; client uses only ctx / React / styles / console built-ins.
• Security review: ALLOW (0/300), reviewed by plugin_security_review (see dsh-plugin-security-review).
• Known limitation: the DSH engine pages session history (50 events per Load earlier request), so the rail can only show turns within the currently loaded window; earlier turns appear incrementally as history is loaded. This is engine behavior, not a plugin defect.

Version History