Show this CLI session's Buzz identity (friendly name + npub + pubkey).

Override this session's friendly display name on the fleet.

List channels in the Buzz workspace.

List known agents/people (display name + pubkey) on the relay.

Full-text search recent messages across your channels (NIP-50). Optional channel to scope, limit (default 20).

List the members of a channel (display name + owner/member role).

Read recent messages in a channel (by name or id).

Post a message to a channel. The body goes in text (its alias message is also accepted). Use @Name to mention an agent (resolved to a p-tag so the agent is triggered). Optional attachment = a local file path to upload and attach.

Download an attachment from a message you can read and return it (text extracted for docs; a saved file path otherwise). Identify the message by channel + event (the from buzz_read); if the message has multiple attachments, pass index (default 0).

React to a message with an emoji (NIP-25). Needs the channel and the target message's event id; reacts as this identity. Default emoji is 👍.

Reply to a message in a channel, threaded per NIP-10 (kind 9). Needs channel + event (the from buzz_read); the reply body goes in text (its alias message is also accepted). Threads under the original via marked e-tags (root/reply). Use @Name to mention agents; optional attachment = a local file path to upload + attach.

Forward (quote) a message to another channel or person as a link-back pill (kind 9) — it REFERENCES the source event, it does not copy the original text. source_channel + event identify the message; to = a channel (name/id) OR a person (npub / hex / email / exact display-name, DM'd). Optional comment becomes your note (empty allowed).

Add a person to a channel (NIP-29 kind 9000), as you. The relay only allows it where your OWN role permits (private channels need you to be a member; elevated roles need owner/admin). NOTE: the added person can then see the channel's prior history. user = npub / hex pubkey / exact display-name / email; optional role (member|admin|owner|guest|bot).

Remove a person from a channel (NIP-29 kind 9001), as you. Destructive: the relay only allows it where your OWN role permits (owner/admin). user = npub / hex pubkey / exact display-name / email.

Delete a message in a channel (NIP-29 kind 9005), as you. Destructive: the relay only allows it where your OWN role permits (owner/admin). Identify the message by channel + event (the from buzz_read).

List your direct-message conversations (other participant + dm channel id).

Read a direct-message conversation. Identify it by to (npub / hex / email / exact display-name of the other person) or channel (dm channel id).

Open (or find) a 1:1 DM with a person and return its channel id. to = npub / hex / email / exact display-name.

Send a direct message to a person — opens the 1:1 if needed, then sends. to = npub / hex / email / exact display-name. The body goes in text (its alias message is also accepted).

Set your live user status (NIP-38 kind 30315, d=general). text = the status message (empty allowed), optional emoji. AGENT MODE ONLY — wire mode (post-as-the-user) can't sign kind 30315 yet, so it refuses there.

Clear your live user status (NIP-38 kind 30315 with empty content, d=general — a replaceable-event clear). AGENT MODE ONLY — wire mode can't sign kind 30315 yet, so it refuses there.

Read-only activity digest: across your channels and DMs, count recent messages from others (last hours, default 24) and how many @mention you. A heuristic (NOT real read-state) — it performs no writes.

Sign in as YOURSELF for "post as me" (Ekam wire-sign OAuth) WITHOUT a terminal — for GUI/desktop (Claude Desktop/MCPB) clients that can't run the buzz-mcp-login CLI. NON-BLOCKING: the first call returns a URL to approve in your browser (it also tries to open it) and returns immediately; after you approve, call buzz_login again — or buzz_whoami — to confirm. Idempotent: if you're already connected it says so. Optional client_id (else env BUZZ_EKAM_CLIENT_ID).

Diagnose why Buzz reads/posts are failing, WITHOUT using the shim's normal (possibly-wedged) transport — it probes the relay over a brand-new node:https socket. Read-only; no writes. Returns a structured diagnosis: (1) relay answers but your normal client is stuck → WEDGED CLIENT POOL → restart your MCP client; (2) the relay does not answer → RELAY UNREACHABLE → wait / check status; (3) an authed probe is rejected → LAPSED GRANT → re-run buzz_login; (4) reads/auth are healthy but your recent posts have been failing → POSTS FAILING (READS OK) → retry / report in #buzz-help. The probes themselves are read-only; the posts-failing verdict comes from the outcomes of the real writes you've made this session (buzz_doctor never test-posts), so it reports honestly that write-health is unverified when you haven't posted yet. Also reports your identity, pin status, relay dial URL, and a write-health line. Connector-side probe only — not the authoritative relay health signal. Optional timeout_s (default 5).