Destinations and route priority
Use.logs set #channel to set the general channel. Headless delivers logs exclusively through webhooks; when a send cannot be completed, it queues a retry and does not fall back to channel.send. Dashboard → Logs supports category and event destinations. Active delivery uses this priority: event-specific route → category route → general channel. If a specific destination is missing or no longer resolves to a text channel, delivery continues to the next configured route.
Current categories include moderation, messages, channels, roles, members, server, configuration, giveaways, minigames, security, and bot. .logs off removes the general channel and manual webhook URL. It does not erase history or separate routes configured in the dashboard.
Setup, status, and diagnosis
Prefix commands use the server’s configured prefix (. by default). The /logs group publishes set, setup, status, diagnose, and test; it does not provide recent, search, or export as slash subcommands.
/logs setup channel:#mod-logs saves the destination, creates or reuses the webhook, and sends a real test event. .logs set #mod-logs configures the destination and attempts webhook setup, but it is not the full slash setup. Use .logs diagnose to review Audit Log access, webhook, permissions, intents, delivery mode, and recent errors; .logs test sends a real test entry and distinguishes confirmed delivery, a queued retry, and unconfirmed delivery.
Search and export history
.logs recent [amount] displays up to 20 entries (10 by default). Use a positive amount: the runtime does not normalize negative values. .logs search <query> performs a case-insensitive search across action, actor, target, reason, and ID, and displays up to 15 recent matches. recent and search require Moderate Members.
History is isolated per server. The default limit is 50,000 entries per server; HEADLESS_LOG_HISTORY_LIMIT_PER_GUILD can set it between 5,000 and 250,000. .logs export downloads the server’s stored logs as JSON and requires Administrator; if the file exceeds 7 MB, the command will not attach it and points to the local data file instead.
Permissions and privacy
Configuration, status, diagnosis, test, and export commands requireAdministrator from the user; history commands require Moderate Members. For prefix commands, compatible checks may accept Headless Fake Permissions; a virtual permission never replaces the bot’s own permission. /logs publishes Administrator as its default permission and Headless checks it again locally.
To attribute events, the bot needs View Audit Log. It needs Manage Webhooks to create or repair webhooks. Log transport is webhook-only and has no channel.send fallback; the bot’s message permissions do not turn a failed webhook delivery into a confirmed delivery. Diagnosis reports webhook permissions and whether member and message-content intents are available.
A webhook URL is an access credential. Do not post it, share it in screenshots, or store it in public channels. .logs webhook clear removes the manual URL; if it was exposed, also revoke or rotate the webhook in Discord.
Member reports: separate destination
.reportlogs [#channel] configures where staff receive member-submitted reports and requires Manage Server (native or a compatible virtual permission). If no channel is supplied, the command saves the current channel as the destination. This report route does not change the general log channel or .logs category/event destinations; see Moderation and reports for the intake flow.
Steps
1
Choose the general destination
Create or select a private staff channel and run
/logs setup #mod-logs if you want Headless to test delivery during configuration.2
Add specific routes if needed
In Dashboard → Logs, configure category or event destinations. Valid event routes take priority over category and general destinations.
3
Check permissions and delivery
Run
.logs diagnose and .logs test; confirm that webhook delivery is reported as complete. If delivery is queued or fails, check Manage Webhooks, the selected route, and the error; there is no direct-send fallback.4
Restrict queries and exports
Grant
Moderate Members for history queries; reserve Administrator for configuration and export. Share JSON only with authorized staff.Commands by workflow
Log destinations and webhook
Slash setup and diagnostics
/logs setup
.logs set
.logs status
.logs diagnose
.logs test
Query and export history
Member-report destination
.reportlogs
Note:
The event sent by /logs setup is real, but it is a config_change diagnostic entry, not a sanction or moderation event. .logs test also tests delivery by creating a log entry.