configure-notifications

To configure Telegram notifications, you provide your bot token and chat ID through a natural-language request. The setup interactively validates your credentials, lets you select session lifecycle events like session-end or input-needed, and persists the configuration to ~/.claude/.omc-config.json.

Yes, you can configure Slack incoming webhooks and Discord webhooks or bot tokens at the same time. The setup process detects each provider, validates credentials independently, and allows you to route specific session events to multiple platforms.

You can route session lifecycle events such as session start, session continuing, session end, and input needed. By default, session-end and input-needed events are selected to alert you when interactive Claude Code workflows require your attention.

No, manual editing is not required. The setup uses an interactive provider detection and credential validation process driven by natural-language requests, automatically persisting all Telegram, Discord, and Slack settings directly to ~/.claude/.omc-config.json.

The setup includes an optional end-to-end test message workflow to verify connectivity. After configuring your Slack incoming webhook and selecting events, you can trigger a test message to confirm the endpoint is correctly receiving notifications.

A chat ID is required for Telegram bot notifications because it specifies the exact destination conversation for your alerts. The setup validates both the bot token and chat ID together to ensure session lifecycle events are routed to the correct chat.