Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clarion.cantina.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Notifications keep your team informed about what Clarion is doing, and let agents reach you when they need approval or clarification before continuing.

​
Two kinds of notifications

In-app notifications alert you to things that happened: an incident was assigned to you, a task is overdue, an agent finished a triage. They appear in the notification tray. Human input notifications are active requests from agents that need a response before execution can continue. They’re delivered through your preferred channel and resume the agent run when you reply.

​
Channels

Notifications can be delivered through:
  • Slack: App messages with interactive buttons for approval and clarification.
  • Microsoft Teams: Same flow, in your Teams workspace.
  • Telegram: Bot messages.
  • SMS: Notification only. Used for high-urgency events; SMS does not support interactive approval or clarification.
  • Phone call: Voice escalation for the most critical events.
  • Email: Non-blocking updates.
Each member sets a preferred communication channel in their settings, and Clarion routes notifications accordingly.

​
Human input types

  • Approval: Yes / no on a tool the agent wants to run (e.g., “Suspend user account?”).
  • Clarification: Structured options (“Which user is this?”) or freeform input (“Describe the maintenance window”).
Each request has a timeout. On timeout, the agent either auto-aborts the action or auto-escalates to a backup channel, depending on the skill configuration.
Approval requests for tool calls are an explicit safety boundary. Agents can never execute a gated tool without a human response. The run pauses until you reply or the timeout fires.