Buzz guide

Prepare the existing bot#

Ask your Buzz relay administrator for the bot's private key and current JSON auth tag. This integration uses the SkillBoss Buzz relay at buzz-relay-skillboss.fly.dev. Reuse the bot's existing identity so people do not have to invite a different bot.

In Developer apps, select Buzz and enter both credentials. API callers register platform buzz with credentials private_key (hex or nsec) and auth_tag (the JSON array as a string). Registration verifies relay access through an empty signed query without publishing or reading messages. It does not prove group membership or connect a conversation. Credentials are encrypted and never displayed after registration.

Invite and connect#

Copy the returned bot_public_key and invite that identity to the intended group in your Buzz client. Create a connection with platform buzz, the registered app ID and a session or webhook destination. Open the returned connection instructions, mention the bot in the group and send the displayed LINK code. The page stays pending until a verified signed message claims that connection. If the code expires, request a new one.

AgentSky maintains the relay connection; there is no provider webhook to configure. Existing integrations must import their verified members and groups before retiring their former receiver. Registering an app alone does not migrate identity bindings.

Shared conversations and replies#

Buzz connects a shared group, not a private chat. Replies preserve Markdown and the original reply topic; a connected conversation can continue without repeating the bot mention. Pass the thread_id from signed message.received events unchanged when replying through the API. A group connection does not authenticate every participant to your product: webhook consumers must authorize the actual sender and shared audience.

Native attachments, edits, reactions and streaming are not supported. Share accessible file links and send corrections as new messages. An uncertain delivery returns an error instead of automatically sending again; check the group before retrying to avoid duplicates.

Recovery#

If registration is rejected, check that the private key and auth tag belong to the same currently authorized relay identity. A not-configured result requires the deployment administrator to enable relay forwarding. If the connection stays pending, confirm the bot is in the group and that the message mentions it with the complete unexpired code. Disconnect the conversation to stop routing new messages. Revoking the app also removes its relay subscription when the worker reconciles.