ディレクトリに戻る

dsh-connection-card-host-preview

メンテナンス: 活発

noob-stupid/dsh-connection-card-host-preview

DSHセッション間の状態を保持した接続を、カード型プラグインで構成するためのホスト機能。

GitHub で見る
$ dsh plugin add dsh-connection-card-host-preview

インストール方法

dsh には中央のインストールコマンドはありません。このプラグインのエントリ(README に記載)をプロファイルまたはパッチ設定に追加し、再起動します。

インストールの仕組み

1

スター

0

フォーク

TypeScript

言語

MIT

ライセンス

2026-09-29

作成日

2026-10-26

最終プッシュ

README

dsh-connection-card-host

中文 | English

Contribute: Card & adapter list → · Contribution guide → · 中文清单 Any ordinary DSH plugin can be listed as a card. One row per PR, with evidence.

Let your DSH sessions see each other, talk to each other, and share tools — without getting in each other's way.

Running several DSH sessions at once (one researching, one coding, one running experiments) is normal — but they're isolated: they can't see what the others are doing, and can't hand conclusions over.

This plugin makes a connection a first-class object in DSH: sessions are nodes, a connection is the container, cards are connection-scoped plugins.

In practice (screen recording)

Dragging a connection line out from the anchor beside the composer

Structure (diagram)

Drag-to-connect structure: anchor → session row → rail

Left: the real thing (source video) · Right: the same action as a diagram, showing the toggle semantics


Contents


What it does

See each other Look up which files the other session is editing, how far its plan has got, what tools it last used — collected automatically, no effort required from the other side
Talk to each other Send a message with one of three urgencies you choose: notify only (no interruption) / queue / interject
Share tools Mount cards on a connection: a card can provide tools to the sessions, even with tens of MB of real dependencies
Shared premises A "convention box" holds what you agreed on: interfaces, units, naming, who owns what
Stay out of the way Awareness is pull-based — zero cost unless the other side asks. Unrelated connections never interrupt you

Line colour shows the permission in that direction: grey = read-only, blue = can suggest, orange = can write; the two ends can differ


Quick start

  1. Connect: hold the circle to the left of the composer (or the … on a session row) and drag it onto a row in the session list.

Drag from the anchor (recording)

Dragging an arc out from the anchor beside the composer

Drag from a session row → after connecting (recording)

Dragging from a session row; after release a rail appears with per-end permission dots

anchor source video · session-row source video

  • Toggle semantics: drop on an unconnected row = connect; drop on an already connected row = disconnect (the hover hint tells you which)
  • You can also pick two sessions from the "Connections" panel in the sidebar
  1. Done. Both ends get one quiet notice (who you're connected to, what it enables) — nobody is interrupted.
  2. Want more detail? Open "Connections" in the sidebar, or have the session call connection_peer_work itself.

Once connected, a rail appears beside the session rows, with a coloured dot at each end — that's the permission for that direction:

Connections panel: permissions are set per direction, and cards, awareness and conventions all live under the same connection


Three layers: awareness / conventions / messaging

These are separate, because their costs differ enormously:

Layer Mechanism Enters the other's context? Forces the other to act? Cost
A. Work state pull (the other asks) only when it asks ❌ no 0
B. Convention box pull (the other asks) only when it asks ❌ no 0
C. Messaging push (into its inbox) unconditionally ✅ always every message

The key fact: in DSH, delivering a message forces the other session to run a turn — the agent loop has no "saw it but ignored it" state. So "talking" and "being aware" have to be built separately: to make the other side know, use A/B; only to make it act, use C.

A. Work state (automatic, zero cost)

Collected from runtime events — it asks nothing extra of the model:

【session-bd5ac1b1】
status: running a command (2s ago)
recently touched: water-boat/src/water.js
progress: turn 69 / step 39

B. Convention box (explicit, zero cost)

What you agreed on: interface signatures, units, coordinate systems, naming, who owns what. Editable in the panel; sessions read and write it with connection_conventions / connection_declare.

GitHub で README 全文を読む →

DSH Plugins は DeepSeek Harness プラグインの独立したコミュニティ ディレクトリです。DeepSeek との提携・公認はありません。サードパーティ製プラグインはセキュリティ監査を受けていません。インストール前にソースコードをご確認ください。

DeepSeek Harnessの新着プラグインを毎週お届け。スパムはありません。