{"version":"2.1.229","anchor":"remote-clients-are-told-which-slash-commands-need-the-termin","canonical_anchor":"remote-clients-are-told-which-slash-commands-need-the-termin","heading":"Remote clients are told which slash commands need the terminal","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/remote-clients-are-told-which-slash-commands-need-the-termin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Remote clients are told which slash commands need the terminal\n\nPhone and remote interfaces are now told which slash commands only make sense in a terminal.\n\n**What**\n\nThe session init payload sent over the control protocol now includes an optional list of slash commands whose behaviour only makes sense in a local terminal, such as `\/color`, so phone and remote interfaces can hide them. The list is sent only when it is non-empty.\n\n**Evidence**\n\n`Subset of slash_commands whose UX is bound to the local terminal (e.g. exit, statusline).`\n\n- Area: Remote Control\n- Names: `\/color`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}