{"version":"2.1.238","anchor":"slash-commands-can-report-being-unavailable-to-coordinators-","canonical_anchor":"slash-commands-can-report-being-unavailable-to-coordinators-","heading":"Slash commands can report being unavailable to coordinators and workers","tier":"soon","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/slash-commands-can-report-being-unavailable-to-coordinators-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Slash commands can report being unavailable to coordinators and workers\n\nNew wording exists for slash commands that a coordinator or worker cannot trigger for you.\n\n**What**\n\nNew 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.\n\n**Evidence**\n\n`by the coordinator or by workers`\n\n- Area: Slash Commands\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}