Sticky messages

Use /config sticky-message to create and manage a message independently from automatic threads. Every new human message posts a fresh copy at the bottom of the channel and then deletes the previous copy. Bots, webhooks, and sticky copies are ignored to prevent loops.

Content

The content modal offers three optional inputs, but you must use exactly one: up to 2,000 characters of Discord Markdown, pasted JSON up to 4,000 characters, or one JSON file up to 64 KiB. Combining inputs is rejected. For embeds or Components V2, export the JSON from Discohook or DWEEB, then paste or upload it directly in the modal.

A payload uses either content and embeds, or flags: 32768 and static Components V2. Auto Threads accepts text displays, containers, sections, separators, media, thumbnails, and URL buttons. Files, polls, menus, and interactive components are rejected. Mentions remain visible but never send notifications.

Classic JSON does not require Components V2: content, regular embeds, embed images, and thumbnails are supported. The panel groups all embed and Components V2 payloads under JSON, while a content-only payload is shown as normal text.

Use Preview message for an ephemeral content preview. Send message publishes the sticky immediately, including its first copy when nobody has posted in the channel yet.

Never provide a webhook URL to an external builder. Auto Threads imports only the message JSON.

Custom profile

The bot sends the sticky by default. First select webhook delivery; the panel then displays a separate profile section where you can choose a username and HTTPS avatar URL. Both the configuring member and Auto Threads must have ManageWebhooks in that channel. Auto Threads creates and recreates the webhook, storing only its identifier and never its token.

The latest-copy identifier remains attached to the configuration without expiration. An inactive channel can therefore resume cleanly months later without searching its history.