{"version":"2.1.248","anchor":"get-settings-is-refused-on-remote-connections","canonical_anchor":"get-settings-is-refused-on-remote-connections","heading":"get_settings is refused on remote connections","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/get-settings-is-refused-on-remote-connections","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### get_settings is refused on remote connections\n\nRemote clients can no longer read back your model, effort or settings-file errors.\n\n**What**\n\nA remote client can no longer read back your applied model, effort and advisor state or your settings-file errors. On a bridge connection (`CLAUDE_CODE_ENVIRONMENT_KIND=bridge`) the `get_settings` control request returns \"get_settings is not available on this connection\" instead of a settings snapshot. Local sessions still get the full snapshot.\n\n**Evidence**\n\n`get_settings is not available on this connection`\n\n- Area: Remote Control\n- Names: `get_settings`, `CLAUDE_CODE_ENVIRONMENT_KIND`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}