Slack notifications

Slack notifications give workspace operators one channel for agent runtime and gateway failures. This is separate from an agent’s conversational Slack connection: one notification app covers the workspace, and operators choose which agents are included.

Connect notifications

Open Settings > Notifications in the Herm web app:

https://herm.run/app/settings/notifications

An owner or admin can select Install app to workspace, approve Prism Agent Notifications in Slack, and choose the destination channel. No manifest or token entry is required. Notifications include all active agents by default. Turn off All agents to select individual agents. Future agents are included automatically only while All agents is enabled.

Notification types

Notification	When it is sent
Sandbox creation failed	A new sandbox or its persistent volume cannot be created after Herm’s existing recovery attempts.
Sandbox startup exceeded 1 minute	A newly created sandbox takes more than 1 minute to become ready. Reused sandboxes and session warmup do not count.
Hermes runtime did not start	The managed Hermes process cannot be launched or exits during startup.
Hermes runtime did not become ready	Hermes starts but its API does not become ready within the cold-start budget. The available runtime error is included when possible.
Session runtime failed	A turn cannot connect to or restore its session runtime after recovery is exhausted, Hermes ends the turn with an error, or an in-progress session is interrupted by a gateway restart. The available error message is included.
Custom tool failed	Herm accepts a custom-tool result with `status: "failed"`. The notification identifies the session and tool request without including tool arguments or result content. Error responses used for conversational Slack recovery do not alert unless they also have failed status.
Agent API returned a server error	An authenticated, agent-scoped gateway request returns a `5xx` response. Organization-level errors without an identifiable agent are not sent.

Delivery behavior

Notifications are best effort. Herm makes one background Slack delivery attempt and does not delay or change the agent request. Failed Slack deliveries are logged but are not retried. Messages include the agent name, session ID when available, and a short failure summary. Credential-shaped values are redacted, summaries are truncated, and customer prompts and tool arguments are not sent. To change the Slack workspace or channel, select Change workspace or channel and repeat installation. Disconnecting removes the workspace notification integration without changing any agent’s conversational Slack connection.

Getting Started

Agents

Sessions and events

Capabilities

Integrations

Credentials

Resources

Slack notifications

Connect notifications

Notification types

Delivery behavior

​Connect notifications

​Notification types

​Delivery behavior

Connect notifications

Notification types

Delivery behavior