Channels & threads

Lockdowns

A lockdown removes send permissions from a role so nobody can talk. It’s the first thing to reach for when something’s going wrong in a channel.

!lockdown

!lockdown #general spam wave

!lockdown all

!lockdown until 2h
!lockdown all until 6pm

!unlockdown
!unlockdown all

Requires Manage Roles. Aliases: lock, l / unlock, ul, uld. lockdown all until 6pm accepts natural language, and respects your timezone if you’ve set one.

Which role gets locked

By default it’s @everyone. If your server gates access behind a member role instead, point it at that:

!lockdown role @Member

Channels to leave alone

!lockdown ignore #staff-chat
!lockdown ignore list
!lockdown ignore remove #staff-chat
!lockdown ignore clear

Ignored channels are skipped by lockdown all, which is how you keep staff coordination working while the rest of the server is frozen. Alias: exempt.

unlockdown all only unlocks channels it locked. Channels that were already private stay private, so you can’t accidentally expose a staff channel by unlocking the server.

Slowmode

!slowmode #general 10s

!slowmode #general 5m getting heated

!slowmode off #general

Requires Manage Channels. Aliases: slow, slowmo, cooldown, cd. Discord’s maximum is 6 hours.

Hiding and revealing

!hide #staff @someone

!hide #staff @Member

!reveal #staff @someone

Requires Manage Channels. hide aliases: private, priv. reveal aliases: unhide, public. With no target, it hides the channel from @everyone. This edits channel overwrites, so it’s the same thing you’d do in channel settings — just faster.

Topics

!topic #general read the pinned messages
!topic remove #general

Requires Manage Channels.

Nuking a channel

!nuke

Clones the current channel — same name, permissions, position, topic — and deletes the original. Instant way to wipe a channel with no history limit. Requires Administrator.

The new channel has a new ID. Anything referencing the old one breaks: pinned message links, webhooks, sticky message configs, counter channels, ticket panels. Re-point those afterwards.

Scheduled nukes

!nuke add #daily-chat 1d
!nuke list
!nuke view #daily-chat
!nuke remove #daily-chat
!nuke clear

Wipes the channel on a repeating interval. Popular for daily-reset channels and temporary event channels. nuke clear needs Manage Channels and Manage Messages; the rest need Administrator.

The message it posts

After each scheduled nuke mira posts a line in the fresh channel. Replace it with any script — either as a trailing argument on nuke add, or on its own afterwards:

!nuke add #daily-chat 1d {title: fresh start}{description: back again {nuke.next.relative}}

!nuke message #daily-chat gm, wiped every {nuke.interval}

!nuke message #daily-chat next wipe <t:{nuke.next}:R>

!nuke message view #daily-chat

!nuke message remove #daily-chat

On top of the usual variables, a nuke message gets {channel} (the freshly created channel) and {moderator} (whoever scheduled it), plus a full set for the interval and for both nukes either side of the message. The interval — {nuke.interval}

Variable	Example
`{nuke.interval}`	`12 hours`
`{nuke.interval.long}`	`12 hours`
`{nuke.interval.short}`	`12h`
`{nuke.interval.seconds}`	`43200`
`{nuke.interval.minutes}`	`720`
`{nuke.interval.hours}`	`12`
`{nuke.interval.days}`	`0`

The timestamps — {nuke.next} is the nuke still to come, {nuke.last} is the one that just happened. Both take the same suffixes.

Variable	Example
`{nuke.next}`	`1789367400`
`{nuke.next.unix}`	`1789367400`
`{nuke.next.timestamp}`	`1789367400`
`{nuke.next.relative}`	in 12 hours
`{nuke.next.short}`	14 September 2026 06:30
`{nuke.next.long}`	Monday, 14 September 2026 06:30
`{nuke.next.date}`	14 September 2026
`{nuke.next.time}`	06:30:00
`{nuke.next.iso}`	`2026-09-14T06:30:00+00:00`

The bare {nuke.next} is plain unix seconds precisely so you can build your own Discord timestamp around it — <t:{nuke.next}:R>, <t:{nuke.next}:F>, whatever style you want. The named suffixes are there when you can’t be bothered. Both are covered in full under timestamps & durations.

nuke view and nuke list both show which channels have a custom message. If a custom message ever fails to send, mira falls back to the default and tells the server owner why.

Threads

!thread lock
!thread close
!thread open
!thread rename bug reports
!thread delete
!thread unlock

Requires Manage Threads. Each takes an optional thread and reason — omit the thread to act on the one you’re in. Aliases: threads, t.

Command	Aliases	Effect
`thread lock`	`l`	No new messages, stays visible
`thread unlock`	`ul`	Allow messages again
`thread close`	`archive`	Archive it
`thread open`	`unarchive`, `reopen`	Bring it back
`thread rename`	`name`	Rename
`thread delete`	—	Delete permanently

Preventing auto-archive

Discord archives inactive threads on a timer. To keep one alive indefinitely:

!thread add #important-thread
!thread list
!thread unwatch #important-thread
!thread clear

Requires Manage Channels. Watched threads are automatically unarchived whenever Discord archives them.

To create a thread on every message in a channel automatically, see autothreads.

Command reference

Command	Permission	Description
`lockdown [channel] [reason]`	Manage Roles	Lock a channel
`lockdown all [reason]`	Manage Roles	Lock every channel
`lockdown until <time>`	Manage Roles	Lock until a time
`lockdown all until <time>`	Manage Roles	Lock everything until a time
`lockdown role <role>`	Manage Roles	Which role gets locked
`lockdown ignore <channel>`	Manage Roles	Exempt a channel
`lockdown ignore list`	Manage Roles	View exemptions
`lockdown ignore remove <channel>`	Manage Roles	Un-exempt
`lockdown ignore clear`	Manage Roles	Clear exemptions
`unlockdown [channel] [reason]`	Manage Roles	Unlock
`unlockdown all [reason]`	Manage Roles	Unlock everything it locked
`slowmode [channel] [delay]`	Manage Channels	Set slowmode
`slowmode off [channel]`	Manage Channels	Remove slowmode
`hide [channel] [target]`	Manage Channels	Hide from a member or role
`reveal [channel] [target]`	Manage Channels	Reveal again
`topic [channel] <text>`	Manage Channels	Set the topic
`topic remove [channel]`	Manage Channels	Clear the topic
`nuke`	Administrator	Clone and delete the channel
`nuke add <channel> [interval] [script]`	Administrator	Schedule recurring nukes
`nuke message <channel> <script>`	Administrator	Customize the post-nuke message
`nuke message view <channel>`	Administrator	Preview it
`nuke message remove <channel>`	Administrator	Restore the default
`nuke list`	Administrator	View scheduled nukes
`nuke view <channel>`	Administrator	Inspect one
`nuke remove <channel>`	Administrator	Cancel one
`thread lock/unlock/close/open`	Manage Threads	Thread state
`thread rename [thread] <name>`	Manage Threads	Rename
`thread delete [thread]`	Manage Threads	Delete
`thread add <thread>`	Manage Channels	Prevent auto-archiving
`thread list`	Manage Channels	View watched threads
`thread unwatch <thread>`	Manage Channels	Stop watching

Start here

Security

Restore

Moderation

Server setup

Last.fm

Social

Utility

Channels & threads

Lockdowns

Which role gets locked

Channels to leave alone

Slowmode

Hiding and revealing

Topics

Nuking a channel

Scheduled nukes

The message it posts

Threads

Preventing auto-archive

Command reference

​Lockdowns

​Which role gets locked

​Channels to leave alone

​Slowmode

​Hiding and revealing

​Topics

​Nuking a channel

​Scheduled nukes

​The message it posts

​Threads

​Preventing auto-archive

​Command reference

Lockdowns

Which role gets locked

Channels to leave alone

Slowmode

Hiding and revealing

Topics

Nuking a channel

Scheduled nukes

The message it posts

Threads

Preventing auto-archive

Command reference