{"version":"2.1.269","anchor":"custom-output-styles-can-be-blocked-when-using-remote-contro","canonical_anchor":"custom-output-styles-can-be-blocked-when-using-remote-contro","heading":"Custom output styles can be blocked when using Remote Control \/ relayed sessions","tier":"notice","area":"Output Style","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/custom-output-styles-can-be-blocked-when-using-remote-contro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Custom output styles can be blocked when using Remote Control \/ relayed sessions\n\nCustom output styles can't be selected or changed over Remote Control or in relayed sessions\n\n**What**\n\nClaude Code now blocks selecting a custom (non-built-in) output style when connected through Remote Control or via a relayed message, showing the message: \"Custom output styles can't be selected over Remote Control or from a relayed message. Select one in the session itself, or pick a built-in style here.\" It also now blocks changing output styles at all from sessions that don't load local settings.\n\n**Why**\n\nCustom output styles depend on settings stored locally, so a remote or relayed session that doesn't have access to those local files can't safely apply one; built-in styles remain available in those cases.\n\n- Area: Output Style\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}