Skip to content

← All releases

Command rules for message, person and palette commands

A community’s Who and where can now be set for each of an app’s menu commands, and a command kept to some channels no longer runs from a page with no conversation.

Community settings › Integrations › Commands lists each installed app with the commands it adds to a message’s menu, a person’s menu and the palette. Each has its own Who and where, and the app has one for everything of its. A command’s own rule is followed over its app’s.

An app’s slash command can now be a family of sub-commands, and groups of them, each with its own options — /perms add, /perms role add — which Kemble Circle’s message box offers and draws. A command can also take a file: you choose one of your own uploads, and the app is handed an address that opens that one file for 15 minutes.

A rule that keeps a command to some channels now holds everywhere: a palette shortcut or a person’s command run from a page with no conversation is refused before the app hears of it, and is no longer offered there. A command kept to a role or to some channels is not run from a direct message either, where no community’s rule used to be asked. Whoever manages the community can always run its commands.

Also in Kemble Circle: Report community in a community’s menu, on its card, in Explore and in a preview, sent to Kemble’s safety team; #channel links and the # list for channels named in any script, and for voice rooms and stages; an app’s suggestion now sends its value; Ignore and Report user on a friend’s menu; and the sign-in page opens for the product a device last used, with a line to the other.

More from October 2026