{"version":"2.1.234","anchor":"remote-control-handshake-now-sends-the-session-s-slash-comma","canonical_anchor":"remote-control-handshake-now-sends-the-session-s-slash-comma","heading":"Remote-control handshake now sends the session's slash commands","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/remote-control-handshake-now-sends-the-session-s-slash-comma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Remote-control handshake now sends the session's slash commands\n\nRemote clients now receive your session's slash command list when they attach, so they can offer them.\n\n**What**\n\nWhen a remote client attaches to a session, the acknowledgement it gets back now lists the session's available slash commands, so the client can offer them. If the command list cannot be produced, the acknowledgement carries an empty list rather than failing the handshake.\n\n**Details**\n\n- The empty-list fallback is recorded as `bridge_initialize_commands` with `get_commands_threw`.\n- Runs on every bridge transport initialize; no gate.\n\n**Evidence**\n\n`bridge_initialize_commands`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}