New wording exists for slash commands that a coordinator or worker cannot trigger for you.
Two message variants for programmatically-unavailable commands are chosen by session kind, with no command in the build shown using them.
What's wrong with this entry?
New wording exists for commands that cannot be triggered programmatically. Outside a multi-agent session it asks you to run the command yourself; inside one it says the command cannot be invoked by the coordinator or by workers. Which variant appears is chosen at runtime from the kind of session, and nothing in this build shows which commands use it.
by the coordinator or by workers
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command