Notifications

Agents work without you watching. Hyperbeam tells you when one of yours needs you, so you do not have to keep its page open.

What you are told

You get a notification when an agent you started:

• asks you a question,
• finishes a turn and is waiting to hear what is next, or
• fails.

Some things are left out on purpose:

• Workers under a conductor report to the conductor, not to you. You hear from the conductor.
• A turn you interrupted is not news to you.
• A turn that ends with a question is one notification, the question.
• A turn that ends with your next message already queued is not announced: the agent is not waiting.

Other people’s agents never notify you. The board and Activity show what the whole team is doing.

In Hyperbeam

Notifications in the sidebar lists them, newest first, with a count of the ones you have not read. Select one to open the agent’s page.

A notification is marked as read when you open the agent’s page or reply to the agent, from anywhere, including a chat thread. If you are already on the agent’s page when it happens, it arrives read. Mark all read clears the rest.

Notifications are kept for 30 days.

In Slack or Discord

The chat app can also send you each notification as a direct message, with a button that opens the agent’s page. Turn this on for yourself under Settings → My account → Notifications. It needs two things first:

1. An admin has connected the Slack or Discord app.
2. Your chat account is linked to you. Mention the bot and it will link you, or send you a link.

The message goes to every account you have linked on that platform. Slack and Discord are separate switches.

On Discord the bot can only message you if you allow direct messages from members of the server you share with it. A message that cannot be delivered is dropped; the notification is still in Hyperbeam.

To answer a question from a direct message, open the agent’s page with the button. Replies to the bot’s direct message are not passed to the agent.