During launch, automations are supported only in public Discord channels. Private channels and direct messages are not supported.
Parent-channel scope
An automation authored in a native thread belongs to the verified parent channel. The parent channel determines where the automation appears in lists, which authorization rules apply, which messages can match, and where authorized users manage it. The native thread remains the conversation context for authoring, confirmations, controls, and management-card updates. These interactions return to the thread where the automation was created.Delivery by trigger
Automation delivery depends on the trigger type:
Confirmations, controls, and management-card updates return to the originating native thread, regardless of how run results are delivered.
Compatibility with thread-scoped automations
Automations saved against a native thread continue to match, appear in lists, and accept authorized management actions. No customer migration is required. Editing an existing scheduled, recurring, or webhook automation updates its delivery to a new parent-channel message for each run. Message-triggered automations continue to reply to each matching message in its originating thread.
What’s next
Set up CodeRabbit Agent for Discord
Connect an eligible community and configure CodeRabbit Agent for Discord.
Usage and limits
Review the Discord surfaces and launch limits that apply to automation runs.