{"version":"2.1.248","anchor":"config-now-separates-a-refused-setting-from-a-failed-save-an","canonical_anchor":"config-now-separates-a-refused-setting-from-a-failed-save-an","heading":"\/config now separates a refused setting from a failed save, and hides save detail remotely","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/config-now-separates-a-refused-setting-from-a-failed-save-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### \/config now separates a refused setting from a failed save, and hides save detail remotely\n\n\/config now tells a refused setting from a failed save, and hides paths on remote sessions.\n\n**What**\n\nSetting a value with `\/config key=value` now distinguishes a setting Claude Code refused to change from one it tried and failed to save. Refusals show their own message verbatim. On remote sessions, save failures are replaced with \"Couldn't save this setting (detail withheld on this connection).\" so local paths and error text do not leave the machine. Invalid keys and values are now escaped before being echoed back.\n\n**Details**\n\n- The withholding applies only to save failures, and only when the session is remote; locally the full detail is still shown.\n\n**Usage**\n\n`\/config editorMode=vim` **Evidence** `Couldn't save this setting (detail withheld on this connection).`\n\n- Area: Configuration\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}