{"version":"2.1.318","anchor":"project-scoped-settings-source-label-set-with-project","canonical_anchor":"project-scoped-settings-source-label-set-with-project","heading":"Settings from a project now show as set with \/project instead of --settings","tier":"notice","area":"Configuration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/project-scoped-settings-source-label-set-with-project","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Settings from a project now show as set with \/project instead of --settings\n\nWhen an attribution project is set, settings from that source are labelled \"set with \/project\" instead of \"--settings\"\n\n**Unclear.** Whether a \/project command is available to type in this release is not confirmed.\n\n**What**\n\nClaude Code shows where each of your settings came from. When the `attributionProject` setting is in use, settings from one source are now labelled \"set with \/project\". Before, the same source was labelled `--settings`, after the command-line option that passes in a settings file.\n\n**Why**\n\nThe new label points to a `\/project` command as the way these settings were supplied.\n\n- Area: Configuration\n- Names: `\/project`, `attributionProject`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}