{"version":"2.1.271","anchor":"slash-command-resolution-helpers-reworked-for-poll-eventpro","canonical_anchor":"slash-command-resolution-helpers-reworked-for-poll-eventpro","heading":"Slash-command resolution helpers reworked for poll-event\/prompt modes","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/slash-command-resolution-helpers-reworked-for-poll-eventpro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Slash-command resolution helpers reworked for poll-event\/prompt modes\n\nSlash-command resolution logic reworked to distinguish bash, poll-event, and prompt modes\n\n**What**\n\nThe internal logic that determines whether something counts as a resolvable slash command was reworked. It now explicitly treats `bash` and `poll-event` modes as never resolvable, while `prompt` mode is handled separately, including resolving MCP (Model Context Protocol) and non-MCP command names and following subcommand redirection targets.\n\n**Why**\n\nThis is internal logic that governs how slash commands get resolved depending on the context they're invoked from; it should make command resolution more consistent across these different modes.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}