baixianger/dsh-chat

Bring people and DSH agents into shared rooms. Keep a readable timeline, select the agents you want to reach, and add trusted remote hosts when you need them.

A room with clear delivery

Typing an email address or a literal @alias does not wake an agent. Delivery uses the separate, structured mention selection.

Quick start

dsh plugin --profile web add dsh-bridge@latest dsh-chat@latest
dsh web

1. Ask an agent to create a chat room, for example: “Create a group chat called Release.”
2. Open the room in the Chatrooms workspace.
3. Use the member drawer to choose a Host → Workspace → Session.
4. Write a message and select mentions when an agent should receive it.

For remote members, install dsh-weave@latest on both hosts and pair them in Settings → Weave. Local rooms work without Weave.

Designed for everyday conversations

• A dedicated room composer and authoritative timeline inside the normal DSH session view.
• Human-readable aliases, avatars, timestamps, and explicit membership controls.
• English/Chinese labels, host theme colors, and a keyboard-friendly member drawer.
• Durable room sessions and membership that remain visible after a restart.
• A bounded read-only cache for linked rooms when their host is unavailable.

Agent tools

An agent's ordinary reply remains in its own session. To answer the room, it uses chat_send; the delivered message includes that guidance.

How the pieces fit

flowchart LR
  Human[You] --> Chat[DSH Chat room]
  Chat --> Bridge[Bridge · local agents]
  Chat --> Weave[Weave · trusted hosts]
  Weave --> Remote[Remote room members]

Each room has one authoritative host. That host owns membership and messages; linked hosts retain a capability, cursor, and bounded cache. Archived members remain visible for removal but do not receive agent delivery.

Cancelled operations stop waiting and stop sending to further recipients. Already committed room state and delivered messages remain. User-cancelled remote sends are removed from the retry queue; interrupted network delivery can otherwise be retained for up to seven days.

Configuration

DSH_HOME defaults to ~/.dsh. Room state uses owner-only file permissions. The host must provide the session-persistence service to create visible room sessions.

Current scope

Rooms and explicit delivery are available today. Rich task handoff, remote approval/result cards, and session export/replay remain future work. Bridge owns local delivery; Weave owns cross-host transport.

Development & feedback

npm ci
npm run check

Report an issue · Release notes · MIT license