{"version":"2.1.318","anchor":"new-project-command-off-unless-tengu-gentle-cupcake-is-on","canonical_anchor":"project-command-to-name-a-claudeai-project-for-usage-repor","heading":"New \/project command names the claude.ai Project for a session's usage reports","tier":"use","area":"Slash Commands","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/new-project-command-off-unless-tengu-gentle-cupcake-is-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### New \/project command names the claude.ai Project for a session's usage reports\n\nA new \/project command, gated by tengu_gentle_cupcake, sets attributionProject for usage reports; IDs may start with chan_ and --settings is a source\n\n**Unclear.** It is not clear who passes the eligibility check the command also requires.\n\n**What**\n\nA new slash command, `\/project`, sets which claude.ai Project a session's usage is reported under. Its description is \"Set the claude.ai Project for this session's usage reports\", and it takes `[Project ID or claude.ai address] [--save] | clear [--save]`.\n\n- Choosing a Project: you give a Project ID or a claude.ai\/project address. `--save` stores it as `attributionProject` in your local settings, and `clear` removes it.\n\n- Requirements: you must be logged in with claude.ai and connected directly to Anthropic, not in a cloud session, and `CLAUDE_CODE_ATTRIBUTION_HEADER` must not be set to 0. Managed settings can block the command, and the `CLAUDE_CODE_ATTRIBUTION_PROJECT` environment variable takes priority over it.\n\n- Availability: the command only appears when an eligibility check passes and the remote flag `tengu_gentle_cupcake` is true. Nothing has been read about that flag. Its built-in fallback is false. The command also works in non-interactive sessions.\n\n- Status lines: the session reports \"This session names claude.ai Project ${r.name} for usage reports (${r.origin})\" or \"This session names no claude.ai Project for usage reports.\"\n\n- Where the setting came from: the origin is now worked out in one shared place. The source 'harness' is shown as `CLAUDE_CODE_ATTRIBUTION_PROJECT`, and 'admin_default' as \"your organization's default\". The existing 'user' and 'project' settings labels are unchanged. A setting given with `--settings` is now shown as \"attributionProject in --settings\".\n\n- Accepted IDs: the `attributionProject` setting now accepts IDs starting with \"chan_\" as well as \"claude_proj_\", and also the UUID of a claude_proj_ Project.\n\n- Error text: a related error now says the session \"is in a claude.ai Project\" instead of \"started inside a claude.ai Project\".\n\n**Why**\n\nWhen the command is available, you can choose which Project your usage counts towards from inside a session, and keep that choice with `--save`. Usage can also now be reported under a new kind of Project, whose ID starts with \"chan_\".\n\n- Flag `tengu_gentle_cupcake`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Slash Commands\n- Names: `\/project`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}