{"version":"2.1.307","anchor":"headless-trust-refusal-now-covers-settings-that-belong-only","canonical_anchor":"headless-trust-refusal-now-covers-settings-that-belong-only","heading":"-p in an untrusted folder now names settings that belong elsewhere","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/headless-trust-refusal-now-covers-settings-that-belong-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### `-p` in an untrusted folder now names settings that belong elsewhere\n\nUnder `-p` in an untrusted folder, Claude Code now first says which settings must move to user or managed settings\n\n**Unclear.** Which settings trigger the new error is not stated.\n\n**What**\n\n`-p` runs Claude Code once without the interactive screen and prints the answer. If the folder has not been marked as trusted, Claude Code refuses to run there. It now first prints a separate error saying certain settings must go \"in user or managed settings instead.\" User settings are your own personal settings file; managed settings are ones set by an administrator. The usual message about the folder not being trusted follows.\n\n**Why**\n\nThe refusal is now clearer about what to fix when running in an untrusted folder without the interactive screen.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}