Skip to main content

​
Behavior

.afk [reason] stores the reason and timestamp. When someone mentions an AFK member, Headless replies with the reason and elapsed time. When that member returns and sends a message, the status is cleared and a short return notice is posted. It also accepts .away and .brb. Mention replies are deleted after 12 seconds and process up to eight distinct mentions per message. Reasons are limited to 300 characters and saved in persistent per-server configuration.

​
.afk — 1

Also works: .afk grabbing lunch, back soon · .away in a meeting

​
/afk

​
.afk — 2

​
/afk

​
Review

.afklist (alias .afks) lists up to 15 active statuses and requires Manage Messages. Mention behavior is restricted to avoid pinging roles or @everyone. .afk and .afklist also have slash bridges. A bridge accepts one generic text field named argumentos; it does not expose a slash option named reason. .afks remains a prefix alias.

​
.afklist

Also works: .afks

​
/afklist

Note: The AFK slash routes are compatibility bridges that forward the argumentos text to the prefix command. To provide a reason, use /afk argumentos:lunch; there is no slash field named reason.
The reason may be visible to anyone who mentions the member. Do not include sensitive personal information.

​
Scope

Status uses the existing afk store; it does not change Discord’s native AFK channel or disconnect voice members. Built-in bot replies (activation, mention, list, and return notices) are in English; member-authored reasons are not translated or replaced.

​
Steps

1

Set a status

Use .afk with a short reason that is appropriate for anyone who mentions you to see.
2

Return with a message

Your first message back clears the status automatically.
3

Review carefully

Use .afklist only when authorized and avoid sharing personal reasons unnecessarily.

​
Syntax and examples

​
.afk