Bringing Buzz to DeepSeek Harness: Taught to Speak Nostr

The DeepSeek Harness (DSH) plugin, dsh-message-gateway, extends the DeepSeek Harness assistant across messaging platforms such as Discord, Telegram, and WeChat. The plugin repository was forked and extended to add the Buzz platform to the list. The forked repository is available on GitHub at https://github.com/Tech-Voyage-Dev/dsh-message-gateway.

Prerequisite guide

Self-Host Block's Buzz: Shared AI Agent Workspace

Learn how to self-host Block's Buzz on a Linux VPS behind Cloudflare DNS. Run a secure, Nostr-powered workspace where humans and AI agents collaborate.

12 MIN READ

The DSH assistant joins a Buzz relay as a member, receives direct messages (DMs) and channel messages where it is @mentioned, and responds through the same per-chat agent pipeline used by the Web UI.

Architecture of the dsh-message-gateway Plugin

The architecture of the dsh-message-gateway plugin splits into two parts:

• Host (Node): gateway-store (credentials, ~/.dsh/gateway.json), platforms.ts (platform definitions + connection tests), routes.ts (/gateway/* endpoints), and bridge-manager.ts (the resident bridges: per-chat independent agent sessions + streamed replies).
• Client (browser): the sidebar "Message platforms" page where you save credentials, test connections, and monitor status.

Adding a new platform involves the following steps:

1. A bridge class — start/stop/status plus an onText(text, frame) callback, mirroring wecom-bridge.ts.
2. Bridge-manager wiring — reuse the existing per-chat pipeline (ensureAgentForKey + pendingMap) and swap in the platform's reply sink.
3. Storage/route wiring — in /gateway/save and /gateway/delete: saving credentials starts the bridge, deleting stops it — plus an autoStartXxx flag so dsh web reconnects on boot.

Building the Buzz Bridge: Nostr Protocol & Event Lifecycle

The DeepSeek Harness was used to implement the Buzz bridge. The implementation conforms to the following Nostr protocol specifications:

The diagram below illustrates how the Buzz bridge bootstraps:

Real-Time Streaming via Nostr In-Place Edits (Kind 40003)

Nostr has no native typing indicator, and events are append-only. To make replies feel responsive and alive, the Buzz bridge simulates streaming using in-place edits as shown below:

• The Buzz bridge publishes a placeholder kind 9 event, then progressively rewrites it with rate-limited kind 40003 in-place edits, before writing the final edit when the agent completes its run. This mirrors the "send then edit" pattern used by Telegram and Discord bridges.

Bridging DeepSeek Harness Workspaces via Chat Commands

The DSH "Workspaces" feature in the Web UI is backed by the workspaceRegistry service (@deepseek-ai/dsh-workspace):

const existing = await ctx.workspaceRegistry.resolveByPath(request.path);

The Buzz bridge exposes a chat command, /workspace <folder>, which registers an existing folder in DSH. Any new session through the gateway attaches to it and appears in the Web UI.

Three design considerations to note:

• Switching folder = new session. cwd is written into the session header at creation and cannot be mutated afterwards.
• Folder must already exist. create rejects non-existent paths.
• Security-sensitive command. Every session operates under an auto-approve policy, granting file access to the target folder.

Step-by-Step Installation & Configuration Guide

1. Run the following commands:

dsh plugin --profile web add https://github.com/Tech-Voyage-Dev/dsh-message-gateway.git

# Start DSH web
dsh web

2. Once the DSH Web UI is opened in a web browser, click on the 'Message platforms' icon:

3. Click on 'Buzz' on the left panel:

4. Click 'Generate keypair' to generate a Nostr key pair. Copy the npub public key somewhere safe, as you will need it later.
5. Enter the 'Relay URL' and 'Channels' (the allowlist of channel UUIDs to subscribe to).
6. Click the 'Save' button.

Saving the form stores the credentials and starts the bridge. The nsec private key is treated as a secret and stored exclusively in ~/.dsh/gateway.json.

Registering the DSH Assistant Keypair on the Buzz Nostr Relay

Add the DSH assistant to the relay as a member. The pubkey will be the npub generated above:

docker compose exec relay buzz-admin add-member --pubkey npub123123123

Add the DSH assistant to a channel. Adding a member registers it on the relay, but the member will not yet appear or be searchable within channels. To add the agent to a specific channel using buzz-cli, note that the --pubkey parameter must be in HEX format, not npub (the buzz-admin add-member command prints the member's HEX pubkey).

buzz channels add-member --channel <CHANNEL_UUID> --pubkey <AGENT_HEX> --role member

CLI guide

How to Install and Use buzz-cli

Step-by-step instructions to install and configure buzz-cli for managing Nostr channels, member keys, and AI agent permissions.

5 MIN READ

Update the DSH assistant's profile on the Nostr relay to a more meaningful display name using buzz-cli:

Send a Wave (Buzz's DM greeting) to the DSH assistant. The wave comes back:

Sending a Wave as a DM to the DSH assistant — the bridge is alive.

Enabling /workspace

Because the allowWorkspace setting defaults to false, issuing the /workspace command is initially rejected:

Enable it in ~/.dsh/profiles/web/cordis.patch.yml, then restart dsh web:

- id: ui-message-gateway
  config:
    allowWorkspace: true

After the restart:

One gotcha: this assumes the workspace folder (TechVoyage in the screenshots) lives in the default user directory. Specify a full path otherwise. Any new session registered under this workspace via Buzz also appears in the DeepSeek Harness Web UI.

Available Commands

Everything that other supported platforms offer works seamlessly on Buzz:

Security in Snapshot

• The nsec lives only in ~/.dsh/gateway.json (0600, atomic write) — never in /gateway/list, never in logs.
• Every inbound event is signature-verified (verifyEvent), deduplicated, self-filtered, and mention-gated before it reaches the agent.
• Workspace registration is config-gated (allowWorkspace: false by default) since gateway sessions auto-approve.

Key Takeaways

The harder part of adding Buzz to dsh-message-gateway was fulfilling the Nostr protocol contract. The existing plugin already provided a architectural foundation for per-chat sessions and command routing, making the bridge integration straightforward.

References:

• dsh-message-gateway architecture guide — extension recipe, module map, security notes (bridges default to hidden)
• nostr-tools — the Nostr library used under the hood
• deer-flow IM channel connections — reference for IM channel connection patterns