{"version":"2.1.251","anchor":"feedback-and-bug-command-availability-checked-in-one-place","canonical_anchor":"feedback-and-bug-command-availability-checked-in-one-place","heading":"Feedback and bug command availability checked in one place","tier":"use","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/feedback-and-bug-command-availability-checked-in-one-place","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Feedback and bug command availability checked in one place\n\nThe switches hiding \/feedback and \/bug now behave the same in menus and commands.\n\n**What**\n\nThe rules that hide `\/feedback` and `\/bug`, namely `DISABLE_FEEDBACK_COMMAND`, `DISABLE_BUG_COMMAND` and `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`, now run through a single shared check that the feedback drafts entry in the settings menu also uses, so the menu and the commands can no longer disagree.\n\n**Details**\n\n- The `CLAUDE_CODE_SEND_FEEDBACK=true` route additionally depends on a remote flag, `tengu_juniper_relay`, which falls back to off.\n\n**Evidence**\n\n`DISABLE_FEEDBACK_COMMAND environment variable`\n\n- Flag `tengu_juniper_relay`: Off in both readings (read for one account on one subscription tier against v2.1.251; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Slash Commands\n- Names: `DISABLE_FEEDBACK_COMMAND`, `DISABLE_BUG_COMMAND`, `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`, `\/feedback`, `\/bug`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}