dsh-session-messaging

Usage

Open two sessions in the same working directory, then ask either model to coordinate. The tools are model-facing; no manual UI is required.

Example prompts:

Use session_peers to see which other sessions are working here.
Send session-b a message: I am editing src/ui.ts and declared it in writeScopes; avoid it.
Check whether anyone else declared a conflicting write scope before you edit src/api.ts.
Pause receiving peer messages for this session.

Tools:

Tool	Arguments	Result
session_peers	none	{ peers: [{ sessionId, status, canReceive, writeScopes }] }
session_send	targetSessionId, message, optional writeScopes, replyTo	{ accepted, messageId, targetSessionId, targetStatus, conflicts }
session_reception	enabled, optional writeScopes	{ enabled, writeScopes }

accepted means the message entered the target's inbox and the session flush acknowledged persistence. It does not mean the peer model processed or acted on it.

Configuration

The bundle row accepts validated configuration; every field has a default:

- id: session-messaging
  name: dsh-session-messaging
  config:
    maxMessageChars: 4000
    maxMessagesPerMinute: 12
    requireTargetOptIn: false   # sessions are open to peers by default
    sameDirectoryOnly: false
    allowSelfSend: false
    allowColdDelivery: true   # resume a persisted target when it is not live