You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extend/customize the slash commands available So that I can have custom bots appear in the matching commands list like:
Why would you like to do it?
I want a way to browse custom commands without needing to look them up or guess at them that is needed now for the conventional match to !some_command <options> that is common in chat bots now.
How would you like to achieve it?
Per room selection of what these are ideally would be great. Such that room admins could decide on integrations for everyone there, instead of a flow to install these for the whole client, or for all channels only.
Presently it's hard to know if there are bots watching for commands at all, and there is no way to discover without knowing the specifics of the bots' monitoring logic (commands/keywords that work) what they may react to.
The text was updated successfully, but these errors were encountered:
Your use case
What would you like to do?
Extend/customize the slash commands available So that I can have custom bots appear in the matching commands list like:
Why would you like to do it?
I want a way to browse custom commands without needing to look them up or guess at them that is needed now for the conventional match to
!some_command <options>
that is common in chat bots now.How would you like to achieve it?
Per room selection of what these are ideally would be great. Such that room admins could decide on integrations for everyone there, instead of a flow to install these for the whole client, or for all channels only.
Have you considered any alternatives?
Open to ideas, related to element-hq/element-web#7702
Additional context
Presently it's hard to know if there are bots watching for commands at all, and there is no way to discover without knowing the specifics of the bots' monitoring logic (commands/keywords that work) what they may react to.
The text was updated successfully, but these errors were encountered: